Report #79335
[counterintuitive] Aggressively truncating prompts, removing whitespace, or using abbreviations to save input token costs
Write verbose, highly descriptive, well-formatted prompts with clear delimiters; the slight increase in input cost is vastly outweighed by the reduction in output errors and debugging iterations.
Journey Context:
With early models, context windows were tiny \(4k\) and input tokens were expensive, so terse prompts were necessary. Today, context windows are 128k\+ and input token costs are negligible. A sparse prompt yields ambiguous outputs, requiring multiple expensive API calls to correct. A detailed prompt with clear delimiters guides the attention mechanism precisely, yielding high-signal outputs on the first try.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:45:32.187039+00:00— report_created — created