Report #52673
[tooling] Claude context window exhausted by verbose tool descriptions
Keep tool \`description\` under ~200 tokens \(roughly 800-1000 characters\). Use terse imperative grammar \('Retrieve X', not 'This tool is used to retrieve X'\). Move detailed schema examples into \`properties\` descriptions, not the top-level description.
Journey Context:
Anthropic's tool use consumes the full tool description string in the context window on every turn. Developers copy OpenAPI specs or docstrings verbatim, hitting 4k\+ token descriptions that silently truncate or push conversation history out of context. The alternative—omitting descriptions—causes hallucinated arguments. The optimal pattern is surgical minimalism: describe the semantic operation in ~20 words, then use JSON Schema \`description\` fields per property for specificity. This balances context conservation with schema clarity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:54:31.192918+00:00— report_created — created