delete-mailbox

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

No annotations are provided, so the description fully carries the transparency burden. It labels the operation as 'destructive', explains 'removes the folder and any messages it contains', and states that explicit user confirmation is required. It could additionally mention irreversibility but 'destructive' implies permanence.

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?

Description is highly concise and well-structured with clear sections: 'Use when:', 'Returns:', 'Do not use when:', 'Safety:'. Every sentence provides essential information without redundancy.

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 covers purpose, usage boundaries, safety implications, prerequisite actions, and return value. With an output schema present (not shown but noted), the description is sufficiently complete for agent decision-making.

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 has 2 parameters with 50% description coverage (account has description, name does not). The description adds indirect guidance for name ('use list-mailboxes first to confirm the exact name') but does not directly describe the name parameter's format or meaning. Account's description is already in the schema. Overall, marginal added value.

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's purpose: 'deleting a mailbox/folder from an account.' It also distinguishes from siblings like rename-mailbox and delete-message, making the function unambiguous.

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 provides 'Use when:' and 'Do not use when:' conditions with alternative tools named (rename-mailbox, delete-message, batch-delete-messages). Also advises prerequisite actions: 'use list-mailboxes first to confirm the exact name' and 'Require explicit user confirmation.'

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