Bulk Delete Emails

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

Annotations already mark the tool as destructive (destructiveHint=true). The description adds value by explaining that deletion is recoverable (moved to Trash), that progress notifications are emitted if a progressToken is provided, and that return counts are provided. No contradiction with annotations.

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?

The description is extremely concise: two sentences plus a brief note about progress and returns. Every sentence adds essential information, with the core action and safety behavior front-loaded.

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 (4 parameters, output schema exists), the description fully covers the action, confirmation requirement, folder parameter context, progress notifications, and return type. No gaps for an agent to misinterpret.

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 75% (emailIds lacks description). The description compensates by explaining the requirement for `confirmed` and the rationale for `sourceFolder` (folder-scoped UIDs). This adds meaning beyond the schema's parameter names and types.

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 verb ('Delete multiple emails') and the resource ('emails'), and importantly clarifies that it moves emails to Trash, not permanently deletes. This distinguishes it from siblings like 'delete_email' (single) or 'empty_trash' (permanent).

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` to execute, and advises passing `sourceFolder` when UIDs come from a folder other than INBOX. It provides clear context for use, though it could explicitly state when not to use it vs. siblings like 'bulk_move_emails'.

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