Report #101362
[cost\_intel] Tool/function definitions inflate the context window and bill as input tokens on every turn
Only register tools the model can actually use in the current step; shorten tool descriptions and JSON schemas; use tool-search or deferred loading so schemas are injected only when needed; consider fine-tuning if you must expose many functions permanently.
Journey Context:
OpenAI injects the full function-calling schema into the system message on every request, and Anthropic does the equivalent for tool definitions. A 500-token schema repeated across 50 turns adds 25k input tokens. Teams often expose their entire toolbox 'just in case,' which can cost more than the actual generation. The quality trap is that overloaded tool sets also confuse the model and increase wrong-tool-call rates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:25:58.330787+00:00— report_created — created