There is a lifecycle to production prompts. Version one is two sentences. Six months later it is four pages of numbered rules, exception clauses, and ALL-CAPS warnings, each added after some output went wrong. Nobody remembers which rules still matter, and nobody dares delete one. This article is about recognizing when length stops helping — and what to do instead of adding paragraph seventeen.
What length buys you, and what it costs
More instruction genuinely helps when the model lacks information it cannot infer: your output schema, your edge-case policies, your domain vocabulary, examples of the target format. Anthropic's guidance is unambiguous that clarity and context improve results — including explaining why an instruction matters, so the model can generalize rather than pattern-match.
But length has three costs. First, dilution: a critical rule buried in a wall of low-stakes style preferences competes for attention with everything around it. Second, contradiction: long prompts accumulated over months often contain rules that conflict, and the model has to guess which wins. Third, money and latency: input tokens are billed on every request, so 3,000 tokens of prompt on a million calls a month is three billion input tokens before any user content — real spend at any tier's input price.
One published, concrete finding worth knowing: for long inputs (20k+ tokens), Anthropic reports that placing your query and instructions at the end, after the documents, can improve response quality by up to 30%. That's a positioning fix, not an instruction-count fix — evidence that structure often beats volume.
When brevity wins
When the model already knows. Instructions that restate common competence ("be accurate", "read the document carefully", "use good grammar") add tokens and nothing else. Modern models don't need to be told to be helpful; they need your task-specific constraints.
When rules can become examples. Anthropic recommends 3–5 relevant, diverse examples wrapped in <example> tags. A single good example often replaces five paragraphs describing the format — and is less ambiguous.
When rules can become schema. If half your prompt describes JSON field names and types, delete it and use structured outputs (output_config with a JSON schema). The schema is enforced; the prose version was a request.
When rules can become a routing decision. If a prompt needs pages of hand-holding to make a smaller model behave, per Anthropic's own guidance the cheaper fix may be a more capable model, not a longer prompt.
When length wins — make it cacheable
Some prompts are legitimately long: a claims-processing assistant may need policy definitions, a glossary, and worked examples. The discipline is to keep the long part stable and let prompt caching absorb the cost. A cached prefix is billed at 0.1x the base input price on hits (after a 1.25x write for the 5-minute TTL), so a long system prompt that never changes costs a fraction of its face value. Minimum cacheable prompt length is model-dependent — 1,024 tokens on Opus 4.8, Sonnet 5, and Haiku 4.5; 512 on Fable 5 — so a long-but-stable prompt is exactly the shape caching rewards.
The pruning routine
Because instruction effects are empirical, prune empirically. Keep the eval set described in running your own evals, then periodically test a shortened prompt against the incumbent: remove the rules nobody can justify, convert format prose to examples or schema, and compare pass rates side by side. Teams are routinely surprised in both directions — some treasured paragraphs turn out to do nothing, and occasionally a "useless" sentence is load-bearing. Use the free count_tokens endpoint to measure what each revision actually weighs; on high-volume routes, tokens saved multiply across every call.
The goal is not minimalism for its own sake. It is a prompt where every line either changes measured behavior or gets deleted — short enough to audit, stable enough to cache, and cheap enough to run at volume.
Where to go next
See context placement for the long-document ordering rules, prompt caching costs for the pricing math, and common prompt anti-patterns for the failure modes bloated prompts breed.