Report #7234
[tooling] Bloating context window with verbose tool descriptions
Keep tool descriptions under 100 tokens focusing on 'what it does' and 'when to use it'; move detailed constraints, valid values, and examples into the JSON Schema parameter descriptions and \`enum\` fields rather than the top-level description prose.
Journey Context:
LLMs use tool descriptions primarily for selection, not learning. Extremely long descriptions with multiple examples consume valuable context window \(often 100-200\+ tokens\) that could be used for actual data. The JSON Schema itself is machine-readable and more precise for constraints. A common mistake is writing 'Example usage: tool\(input='foo', limit=10\)' in the description—this redundancy wastes tokens without improving adherence. Instead, use the schema's \`examples\` field or keep descriptions minimal and precise.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T02:11:25.402901+00:00— report_created — created