Performance guide
Estimate and reduce tool schema token cost
Estimate tool-definition prompt weight and reduce it without deleting the descriptions models need for reliable routing.
Tool definitions consume context. The answer is not indiscriminate minification: names, descriptions, and enum meaning help routing, while duplicated boilerplate and inactive tools often do not.
Read the schema and its provider wrapper as one contract. APITC distinguishes target requirements from portable JSON Schema, applies mechanical repairs only when intent is recoverable, and identifies transformations that can change meaning.
Diagnostic procedure
Repair the schema, then recompile.
- 01
Measure the compiled target
Provider wrappers and strict repairs can materially change size, so measure output rather than only source.
- 02
Prune by turn
Expose the smallest relevant tool set for the current workflow.
- 03
Compress repetition
Shorten duplicated boilerplate before removing discriminating descriptions.
Every request includes 80 tools and repeated authentication prose.
Route first, then provide 5–10 relevant tools with concise, distinct descriptions.
$.inputSchemaClose this objectOpenAI strict requires additionalProperties: false on every object.
$.inputSchemaRequired array is incompleteStrict mode requires every property in required. APITC will make limit nullable.
No account · no upload · no endpoint calledOpen the full tool schema compiler and operating notes →
FAQ
Before you ship
Does APITC upload my schema?
No. Parsing, diagnostics, and compilation run in your browser tab.
Is the compiled result guaranteed to preserve meaning?
Safe repairs are deterministic. When the target provider cannot express a source constraint, APITC labels the transform as lossy instead of hiding it.
Protocol behavior checked against the Gemini function calling guide. Recheck your pinned provider/API version before production deployment.