Delete Email Account

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is known. Beyond that, the description adds what the annotations cannot say: that stored mail is destroyed, that the address stops accepting mail immediately, and that deletes are casing-sensitive while updates are not, with ambiguous matches rejected.

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?

Three sentences, front-loaded with the destructive consequence, then the parameter clarification, then the casing prerequisite. No filler, and the most consequential fact comes first.

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?

With two fully documented parameters and an output schema, return values need no explanation. The description covers the destruction scope and the casing pitfall well. It stops short of stating permission or authentication requirements, which is the only notable gap for a destructive two-parameter tool.

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 coverage is 100%, and the schema already explains that user is the local part before the @. The description nonetheless adds meaning the schema lacks: that deletes must use the exact stored casing while updates resolve case-insensitively and reject ambiguous matches. It adds little about domain, but nothing is missing.

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 first sentence gives a specific verb and resource plus scope: 'Permanently deletes a mailbox and its stored mail.' That is clearly distinct from sibling deletes like delete_domain, delete_forwarder, and delete_domain_pointer, and from create_email_account and update_email_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 names a real prerequisite workflow: call list_email_accounts or get_email_account first and use the exact stored casing. It does not explicitly rule out alternatives or state when not to delete, but for a terminal delete operation the relevant guidance is the lookup step, which is spelled out.

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