m8811_clear_amp_hours

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

The description implies a destructive or high-risk operation requiring confirmation, but annotations declare destructiveHint=false, creating a contradiction. The description adds no additional behavioral context beyond what the parameter already implies, and the contradiction is a serious issue.

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 a single, efficient sentence that conveys both the action and the constraint without redundancy. It is front-loaded with the verb and resource.

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 simple one-parameter tool, the description provides the essential action and confirmation requirement. However, the contradiction with annotations undermines completeness, and it does not specify the exact effect (e.g., resets to zero) or any prerequisites. The output schema covers return values, so no further information is needed there.

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 sole parameter confirm_clear is clearly referenced by the phrase 'explicit confirmation'. The description makes clear that the tool will not clear unless confirmation is given, providing value beyond the bare schema which has no description.

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 the verb 'Clear' with a specific resource 'accumulated amp-hour counter', clearly stating the tool's function. It is distinct from sibling tools which mostly handle setting, measuring, or querying, and the confirmation condition adds clarity.

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 explicitly states the tool should only be used 'after explicit confirmation', providing a clear safety guideline. It does not mention alternatives, but this tool is unique among siblings for clearing amp-hour counters, so the guideline is sufficient.

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