delete_mailbox

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

Discloses the irreversible nature ('drops all messages and webhook subscriptions') and the need for confirm=true, which is critical for a destructive action. No annotations present, so description carries full burden and meets it well.

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?

Two sentences with no filler. Front-loaded with purpose and warnings. Every sentence earns its place.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description covers all necessary behavioral and parameter details, including error cases and prerequisites, making it complete for correct invocation.

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?

Despite 100% schema coverage, the description adds significant extra semantics: resolution behavior for omitted mailbox_id, ambiguity error details, and the implication of project scope. This goes beyond the schema's descriptions.

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 'Delete the project's mailbox' with specific verb and resource. It distinguishes from siblings like create_mailbox and update_mailbox by specifying the irreversible deletion of all messages and webhook subscriptions.

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?

Explicitly requires confirm=true and explains behavior when mailbox_id is omitted, including the ambiguity error for multi-mailbox projects. However, no direct comparison to alternatives or when-not-to-use guidance.

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