delete_mailbox

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

No annotations provided, so description carries full burden. Mentions the empty-folder constraint but omits other critical behavioral details: whether deletion is permanent, what error occurs if preconditions fail, or permission requirements.

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, zero waste. Front-loaded with action, followed by constraint. Efficient and appropriately sized for the tool's complexity.

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?

Minimum viable for a single-parameter tool. Covers the essential constraint but lacks safety warnings appropriate for a destructive operation, especially given absent annotations and no output schema to indicate success/failure modes.

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 has 100% description coverage ('Mailbox path to delete'), so the structured data fully documents the parameter. Description adds no parameter-specific details, meeting baseline expectations for high-coverage schemas.

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?

States specific action (Delete) and resource (mailbox/folder) clearly. Distinguishes from sibling 'delete_email' by specifying folder-level operation, though could explicitly contrast with 'empty_trash' or 'bulk_delete'.

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?

Provides critical prerequisite ('folder must be empty first'), which implies when the tool will fail. However, lacks explicit guidance on when to use versus alternatives like 'empty_trash' or how to handle non-empty folders.

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