Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It adds valuable disclosure: 'Free, no token, no LLM' signals this is a lightweight, deterministic-looking helper, and 'scored by speed gained, accuracy lost, cost saved' explains what the ranking is based on. It does not detail output format or whether any action is taken, but the advisory nature is reasonably clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the scenario, then lists the recovery options and adds a final no-cost guarantee. It is slightly stylized but every sentence contributes useful context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 optional parameters, no output schema, and no annotations, the description gives a clear scenario and expected result but leaves parameter semantics and return structure largely implicit. It is adequate for understanding the tool's purpose but not fully complete for precise invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only says to 'pass your counters' while mentioning token/context/cost budgets generically. It does not explain individual parameters such as recent_actions, nor does it clarify how budgets and usage relate or which inputs are needed for a meaningful result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: it takes budget counters and returns ranked, least-disruptive recovery options. It clearly distinguishes itself from budget_guard by framing itself as the action-oriented follow-up to the alert, and it lists concrete recovery strategies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening question, 'Approaching a token/context/cost budget mid-run?', provides a clear when-to-use condition. It also positions itself relative to budget_guard, though it does not explicitly state when not to use it or name other alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.