Claude Fable 5.2 Effort Levels: Choose with a Small Creative Evaluation

Quick answer

Use the available effort controls on your Claude surface, run the same brief and rubric at two settings, and compare complete accepted outputs, elapsed time and usage. Raise effort only when your task shows a useful improvement.

1. Define what counts as an accepted brief

Use a fictional launch request containing an explicit price, date, audience and one missing field. Before running it, write the acceptance conditions: preserve supplied facts, mark the missing field and finish every requested section.

Keep the task small enough to inspect directly. An impressive paragraph should not compensate for a wrong launch date. Record critical failures separately from stylistic preferences so an average score cannot hide them.

2. Compare like with like

Anthropic’s API guidance names five effort levels and starts Fable at high. App controls and provider availability may differ. Verify the actual control before running your comparison rather than assuming every interface exposes the API settings.

Use the same source packet, prompt, tools and output requirements at each setting. Record the chosen model, setting, elapsed time, usage and any incomplete output. Repeat enough to see whether a difference survives one unusually good or bad run; no fixed sample here establishes a universal winner.

3. Choose for the next production task

If both settings meet the factual and completion checks, compare their observed time and cost for your actual workload. If one repeatedly misses constraints, the cheaper individual request may still require more revision work.

Keep the decision conditional on the task. A short caption cleanup and a long source-reconciliation brief need not share one setting. Manually hand the accepted brief to Ciyo; image-generation settings and Ciyo credit quotes are separate from the Claude reasoning choice.

Copy and adapt this request

Replace the bracketed fields with your own approved information. The requested output is a draft for review; the example has not been run as a model benchmark.

Evaluate this brief using only [FACTS]. Return the requested audience, approved message, composition, unresolved questions and acceptance checklist. Complete every section. Do not invent missing offer details. Use exactly the same request and source packet when comparing available effort settings; record the setting outside the prompt.

Evaluation worksheet

These example checks describe acceptance criteria, not observed model results.

Common mistakes and how to recover

Do not describe this unrun worksheet as a benchmark result. Populate it with actual observations before making a performance claim.

Fast mode and effort are different decisions. A faster service setting does not itself establish that a lower-effort answer meets the same rubric.

Choose a working method and make the handoff

For a solo shop, start with one item and keep the source facts beside the draft. A team should name one approver and keep a dated version so an old comment cannot silently override the current decision. If the input is incomplete, return to the owner of that fact before polishing the artwork.

Use Ciyo for the visual work described here with the controls and models currently offered in your account. Keep the approved copy separately and add exact wording with editable canvas text where needed. A generated picture is a visual draft; inspect its exported file before using it.

• Fable fast mode
• Fable pricing

Sources and further reading

Primary documentation and related guides used for this article. Availability and controls can vary by account; verify them before beginning your own run.

• Anthropic prompting guidance