reset_usage_stats

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered, but the description adds nothing about what actually gets destroyed or whether it is reversible. The most important behavioral detail, that a confirm=true parameter gates the destruction, is left entirely to the schema's name.

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?

One short sentence with zero padding and the action front-loaded. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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?

An output schema exists, so return values need not be explained. However, for an irreversible, non-idempotent mutation tool, the description omits what is lost, how to confirm, and what the result state looks like, leaving the definition inadequate for safe 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?

The single parameter has 0% schema description coverage and the description never mentions confirm or its default of false. For a destructive tool, the meaning and required value of that flag is the key semantic an agent needs and it is missing from both sources.

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?

"Reset local usage metrics" names a verb and a resource and implicitly distinguishes itself from get_usage_stats / get_tool_usage_summary, but "reset" is ambiguous. An agent cannot tell whether this zeroes counters, deletes the stored history entirely, or restores defaults.

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?

There is no guidance on when to call this versus the read-only siblings, and no mention of the confirm gate or any prerequisite. The agent must infer that a confirm flag exists and what value to supply.

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