Delete Mailbox

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

Annotations already include destructiveHint: true, but the description adds no further context such as irreversibility, impact on mailbox data, or any side effects. It simply repeats the operation name, offering no additional transparency beyond the annotation.

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 very concise, but it essentially restates the title 'Delete Mailbox' and does not earn its place. It is not verbose, yet it adds no new information and is not structured to guide an agent beyond the obvious.

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 deletion tool, the description is incomplete. It does not indicate whether the operation is reversible, what happens to the mailbox's emails, or what the response looks like (no output schema). The destructive annotation covers one aspect, but the description itself lacks essential contextual guidance.

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 schema has 100% coverage for the single parameter mailbox_id with a description, so the baseline of 3 applies. The tool description does not add any extra meaning about the parameter beyond what the schema already provides.

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 'Delete a mailbox.' clearly states a specific verb (delete) and resource (mailbox), distinguishing it from sibling tools like mail_mailboxes_list, mail_mailboxes_create, and mail_mailboxes_change_password. There is no ambiguity about the operation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, permanence, or alternative deletion tools for aliases/forwarders. It is purely a restatement of the action.

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