Bulk action by sender

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

Annotations already flag destructiveHint=true, but the description adds valuable nuance: 'Deletion goes to Deleted Items unless permanent: true.' This goes beyond the schema and annotations, disclosing the non-permanent default behavior and the effect of the permanent flag. It also implies the tool is safe to preview via dryRun.

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 zero waste. The primary action and scope are front-loaded, followed by the critical safety tip (dryRun) and the deletion destination nuance. 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's complexity (6 params, destructive nature) and that an output schema exists, the description covers all essential operational aspects: what it does, the default folder, the dryRun safeguard, and deletion behavior. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, with each parameter having a meaningful description (e.g., dryRun 'count only, change nothing', targetFolder 'Required when action = move'). The description adds no new parameter details beyond what the schema already provides, so the baseline 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 states the exact action ('Move or delete EVERY message from a sender') with a specific resource (sender address, folder) and clearly distinguishes it from single-message tools like mail_move and mail_delete. It also specifies the default folder, leaving no ambiguity about scope.

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?

It gives an explicit usage recommendation: 'Use dryRun: true first to learn how many messages match.' This is clear operational guidance. However, it does not explicitly name alternatives or state when to use this tool versus the single-message siblings, leaving some inference to the agent.

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