Wipe disk

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

The description highlights the destructive and irrecoverable nature, which adds context beyond the destructiveHint annotation. It warns about the need for user confirmation, which is not in 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?

The description is extremely concise (3 sentences) and front-loads the core action and warning. Every sentence serves a purpose with no fluff.

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 destructive tool with no output schema, the description covers the essential behavior: what it does, that it's destructive, and the need for confirmation. It does not cover error conditions, but that is acceptable given the simplicity.

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 input schema has 3 parameters with 67% description coverage (disk and confirm described, node not). The description does not add parameter details beyond the schema. The implication of the confirm parameter is clear, but no additional semantic help is provided.

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 'Wipe a disk by writing zeros to all blocks,' which clearly identifies the action, resource, and method. It distinguishes this tool from the many sibling tools that are read-only or non-destructive.

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 says 'DESTRUCTIVE — irrecoverable. Ask the user to confirm before invoking,' providing clear guidance on when to use (only with user confirmation). It does not mention specific alternatives, but the context makes it obvious.

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