Bulk Delete Emails

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

Annotations already indicate destructiveHint: true, but the description adds crucial context: emails are moved to Trash, not permanently deleted, and remain recoverable. This non-obvious behavioral trait is clearly disclosed, and there is no contradiction with the 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?

Three succinct sentences: alias declaration, behavioral summary with confirmation requirement, and parameter guidance. No redundant words; front-loaded with key information. 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?

The description covers the alias, destructive but recoverable behavior, confirmation requirement, and sourceFolder context. It does not explain the return value, but an output schema exists. Account_id is omitted but documented in schema. Overall sufficient for a destructive bulk operation.

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% with emailIds lacking a description. The tool description reinforces the need for confirmed and provides extra context for sourceFolder, but does not add significant meaning beyond the schema for the other parameters. 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?

Description clearly states it is an alias for bulk_delete_emails and performs deletion by moving to Trash. It distinguishes the action (bulk delete) but does not differentiate from closely related sibling tools like move_to_trash or delete_email, leaving some ambiguity about when to choose this tool.

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 provides specific usage conditions (requires confirmed: true, pass sourceFolder when UIDs come from another folder). However, it does not offer guidance on when to use this tool versus alternatives like single delete or move, nor does it mention prerequisites or when not to use it.

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