Delete Mailbox

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

The description states 'This is destructive,' but this is already indicated by the annotations (destructiveHint: true). It adds no new behavioral information beyond what the agent can infer from annotations, such as whether deletion is reversible or what happens to related data (e.g., emails, folders).

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, consisting of two short, front-loaded sentences. No unnecessary words are present.

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?

Despite having an output schema (which explains return values), the description lacks important context for a destructive operation: it does not mention that deletion is permanent, what resources are affected (e.g., emails, app passwords), or how the id parameter is obtained. The tool's completeness is insufficient for an agent to use it safely.

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 covers the single 'id' parameter with a description and pattern. The description does not add any additional meaning about the parameter, but schema coverage is 100%, so the baseline of 3 is appropriate.

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 clearly states the action and resource ('Delete a mailbox'), which matches the name and title. However, it does not differentiate from related tools like shipmail_suspend_mailbox, which could confuse an agent on which tool to use for temporary vs permanent removal.

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 vs alternatives like suspend_mailbox or resume_mailbox. It fails to mention that deletion is irreversible and should be used only when permanent removal is intended, leaving the agent without critical usage context.

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