delete_mailbox

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

Beyond annotations (destructiveHint=true), description adds specifics: IMAP requirement, user confirmation, refusal of non-empty mailboxes, Gmail restrictions, and error types. No contradiction.

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?

Well-structured with bullet points, front-loaded with main purpose. Slightly long but each sentence adds value; could be marginally shorter.

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 complexity (destructive, IMAP, error cases), description covers prerequisites, behavioral nuances, and edge cases comprehensively. Output schema exists but description completes context.

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?

Input schema covers all 3 parameters with descriptions; description adds context (slash-separated for name, display name or UUID for account, default behavior for delete_messages) beyond 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?

The description clearly states the tool deletes a mailbox via IMAP, explains why (AppleScript limitation), and distinguishes from sibling tools like delete_messages.

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 describes when to use (requires IMAP credentials, user confirmation), when not to use (non-empty mailbox by default, Gmail system labels), and alternatives (delete_messages for messages).

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