budget_reset

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

Despite no annotations, the description fully discloses behavioral traits: it is a destructive reset that preserves ceiling, returns success/failure objects, and requires confirm='yes' to avoid accidental resets. The warning about concurrent agents adds context beyond annotations.

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?

Four sentences front-load purpose, then cover error handling, usage constraints, and verification steps without redundancy. Every sentence adds value and the structure is logical.

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?

Given no annotations or output schema, the description fully covers purpose, behavior, error cases, and usage recommendations. It is complete for a simple two-parameter tool and leaves no ambiguous aspects.

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?

Input schema covers both parameters 100%, so baseline is 3. The description adds minimal new information, only reinforcing that confirm must be 'yes' and mentioning error format, which does not significantly enhance the schema's meaning.

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 clearly states the tool resets all agent spend counters to zero while preserving the ceiling, which is a specific verb and resource. It distinguishes from sibling tools like budget_status (reads only) and budget_spend (increments solely).

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?

Explicit guidance is provided: the tool should not be used mid-task with active agents, only at the start of a new task cycle or after agents finish. It also recommends calling budget_status before and after verification and explains the confirm guard prevents accidental resets.

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