Report #59370
[cost\_intel] Function tool definitions consume more context tokens than the actual tool responses save
Minimize JSON schema verbosity \(shorten descriptions, use terse property names, remove examples\) and dynamically inject only the 2-3 relevant tools per query vs the full 20-tool library
Journey Context:
Developers define 20 tools with 500-token schemas each = 10k tokens per request, but the model only calls 1 tool returning 100 tokens. The cost is 10k vs saving a 500-token text response. The trap is assuming tools are 'free' to define. The fix is dynamic tool selection \(only include relevant tools in context\) and aggressive schema minimization \(removing descriptions where possible, using enums instead of descriptive strings\). Alternative of keeping all tools leads to context window bloat and higher costs than not using tools at all.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:08:35.064257+00:00— report_created — created