Report #50558
[cost\_intel] Tool definitions inflate context window by 10-20x the actual tool call tokens
Use tool\_choice: none in rounds where tools aren't needed, and replace complex JSON schemas with simple string instructions for low-complexity tools
Journey Context:
Tool definitions are embedded in the system prompt as JSON schema on every single request. A 500-token schema counts as 500 tokens every turn, even if the tool is never invoked. A tool call response might only be 50 tokens. In multi-turn conversations, early turns pay the full schema tax for all 10\+ tools while late turns only use 1-2. The non-obvious fix is dynamic tool\_choice switching and schema minimization—removing 'description' fields alone saves 30% of schema tokens.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:20:43.850921+00:00— report_created — created