Bulk Delete Emails

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

Beyond annotations (destructiveHint: true), description reveals that emails are moved to Trash and are recoverable, not permanently deleted. This key behavioral detail prevents misinterpretation. 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?

Two sentences, no fluff, front-loaded with key info (alias, behavior, requirements, special parameter note). Could be slightly more structured, but highly efficient.

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?

Covers alias, recovery behavior, required confirmation, and sourceFolder nuance. Output schema exists so return values are documented elsewhere. Lacks explicit comparison to sibling tools like move_to_trash or delete_email, but sufficient for a straightforward destructive 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?

Adds context beyond schema: 'sourceFolder' guidance about folder-scoped UIDs is helpful. Schema already describes confirmed and sourceFolder partially; description reinforces and explains 'why' and 'when' to pass sourceFolder.

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?

States clearly it deletes multiple emails by moving to Trash (recoverable), and identifies itself as an alias for bulk_delete_emails. Distinguishes from permanent deletion and other similar operations.

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?

Provides specific guidance: requires 'confirmed: true', and when to pass 'sourceFolder' (if UIDs from a folder other than INBOX). Does not explicitly list alternatives or when not to use, but the guidance is clear for correct invocation.

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