Report #53448
[cost\_intel] High token costs when using function calling despite short inputs
Trim tool definitions to only required fields \(remove descriptions/examples\) and shard tools across multiple requests rather than sending full schema in every call
Journey Context:
Each tool definition is sent in the context window on every API call. Complex JSON schemas with descriptions, enums, and examples consume 500-2000 tokens per tool. Teams assume tool definition is 'free' like a system prompt, but it's billed as input tokens on every turn. The common error is including full OpenAPI specs as tool definitions. The fix is aggressive minimization: remove all 'description' fields \(saves 20-30%\), collapse nested objects into flat structures, and for >5 tools, split into separate requests with tool\_choice forced, rather than paying for all schemas when only one is used.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:12:33.467788+00:00— report_created — created