Measure how much tool schemas add to every AI request

Why schemas become expensive

Every tool name, description, parameter, enum and example contributes to input. Long descriptions copied across many tools can dominate small user prompts. Nested JSON and verbose examples add further overhead.

Safe optimization order

First remove tools that cannot be called for the current intent. Then deduplicate shared wording and shorten descriptions while preserving parameter semantics. Keep safety-critical constraints and exact enum values.

Validate agent behavior

Varion keeps its proprietary engine implementation private. Commercial evaluation is based on measurable workload-specific outcomes, clear validation boundaries and customer-specific testing rather than disclosure of internal mechanisms. Use the dedicated Token Optimisation product area to evaluate whether the commercial result is suitable for your traffic; no universal performance percentage is promised.

Measurement checklist

1. Choose a representative completed task, not an artificial one-line prompt.
2. Record the selected model, provider input, cached input, output, retries and final result.
3. Change one optimization mechanism at a time so the cause remains visible.
4. Verify required identifiers, tool calls, code changes or business fields.
5. Keep passthrough available when the reduced request does not pass.

Varion commercial evaluation

Varion keeps proprietary product implementation details private. Evaluate Token Optimisation on representative traffic and judge it by the measured commercial result. New verified users receive 100,000 processed input tokens and 50 local test runs.