TokenPad
Building

Tool Description Optimizer

Cut a tool description to the sentence that actually decides the call.

Your input

199 characters1 lines0 tokensor drop a file

Tool Description OptimizerExact
0Token change
Token change0no change
Input tokens0what you pasted
Output tokens0what you would send
Token cost of this result
Output tokens0
As input$0.00
× 100K requests$0.00

Everything on this page runs in your browser. Nothing you paste is transmitted, because there is no server here to transmit it to.

Result
 

Why this is worth an hour

Tool descriptions are the most-repeated text in an agent. Every one is sent on every request, on every iteration. Cutting sixty tokens across a dozen tools is seven hundred tokens off every single call, permanently.

It is also mechanical work with no quality risk, which makes it one of the few optimisations you can do without an evaluation cycle.

What gets removed

Preamble first: "this function is used to" tells the model something it already knows. Then the wordy constructions — "in order to", "is able to", "for the purpose of" — that survive from documentation habits.

The tool also flags descriptions that explain parameters in prose. The schema already declares them, and stating them twice costs tokens while creating a second place for them to drift out of date.

Frequently asked questions

Will a shorter description make the tool fire less reliably?
Only if you remove the condition. Keep the "when" — that is what the model matches on. Remove the implementation notes, the caveats and the parameter prose, which it does not use.
How short is too short?
If it no longer distinguishes this tool from a sibling tool, it is too short. Two tools whose descriptions could be swapped without confusion are a bigger problem than either being long.

More building tools