Report #83213
[cost\_intel] High token usage when using function calling with many tools despite few tool calls
Prune tool definitions to required fields only \(omit long descriptions\), set strict:false to avoid JSON schema bloat, and consolidate tools into fewer, more parameterized functions.
Journey Context:
Every tool definition is embedded in the context window of every request. Ten detailed tools with complex JSON schemas can consume 4,000-8,000 tokens per call. The cost savings from using the tools rarely offset this overhead for simple tasks. Aggressive schema minimization and tool consolidation often reduce costs by 50% without impacting capability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T22:15:37.617721+00:00— report_created — created