Delete mail account

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

Annotations already indicate destructiveHint=true. The description adds value by stating the operation is irreversible and that confirm=true is required, which goes beyond the annotation. It does not contradict the idempotentHint or openWorldHint.

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 two concise sentences, front-loading the action and key constraint (irreversibility, confirm=true). No wasted words.

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 destructive tool with annotations present, the description covers the essential behavior and safety requirement. It does not describe return values (no output schema) or side effects, but the openWorldHint suggests possible extras. Adequate for the complexity.

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 descriptions for both parameters (mail_address with normalization hint, confirm as explicit consent) already cover 100%. The tool description echoes the confirm requirement but adds no new parameter semantics beyond the schema.

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?

Description clearly states the action (delete) and resource (mail account). It also mentions irreversibility and the confirmation requirement, making it distinct from sibling tools like create_mail_account or update_mail_account.

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 emphasizes that the operation cannot be undone and requires explicit confirmation (confirm=true). This provides clear usage context, though it does not explicitly compare with alternatives (there is only one delete mail tool).

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