Bulk Delete Emails

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

The description discloses that emails are moved to Trash (not permanently deleted), emits progress notifications, and returns success/failed counts. This adds substantial behavioral context beyond the annotations (destructiveHint=true).

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?

Three sentences that are front-loaded: the first covers the core action and key behavior, the second adds optional features and return, and the third lists requirements. No extraneous text.

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 output schema exists and annotations provide safety cues, the description adequately covers behavior, requirements, and return values. Minor gaps on rate limits or auth, but overall sufficient for a bulk delete tool.

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?

The description reinforces the schema's explanation for confirmed and sourceFolder, adding critical context about IMAP UID scoping. Schema coverage is 67%, and the description compensates well.

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 emails by moving them to Trash, distinguishing it from permanent deletion and from sibling tools like empty_trash or single delete_email.

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?

The description explicitly requires 'confirmed: true' and advises passing sourceFolder for non-INBOX folders, providing clear context for correct usage. However, it does not compare to other bulk tools like bulk_move_to_trash.

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