reset_query_stats

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

With no annotations provided, the description carries the full burden. It discloses that the operation is a WRITE with medium risk, irreversible, truncates a specific internal table, and that no undo is recorded. It also mentions the dry_run preview option. This is exemplary behavioral disclosure.

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 [WRITE] and risk/irreversibility warnings. It uses a short paragraph plus Args list; no wasted words. Every sentence adds value.

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 and no output schema, the description explains the operation's effect, irreversibility, the dry-run option, and both parameters. It is complete enough for an agent to invoke the tool safely and correctly.

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%, so the description must explain parameters. It does so for both: dry_run ('If True, preview without resetting') and target ('Target name from config; omit for the default'). This fully compensates for the schema gap.

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 states a specific verb ('Reset') and a specific resource ('statement-digest accumulators'), with an immediate note that it truncates performance_schema.events_statements_summary_by_digest. This clearly distinguishes it from sibling tools like kill_session or set_global_variable.

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 description clearly communicates irreversible side effects and recommends dry_run=True for preview, which is valuable usage guidance. However, it does not explicitly state when to use this tool versus alternatives (e.g., when you need to clear aggregated query statistics), though the context makes it evident.

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