Delete Email

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

Beyond annotations (destructiveHint: true, readOnlyHint: false), the description adds that the action is reversible (moves to Trash, not permanently deleted) and idempotent for already-trashed emails. It also explains the confirmation requirement.

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 three sentences, front-loading the key action and behavior, with no unnecessary words. Every sentence adds value.

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 has an output schema (implicitly covering return values) and the description covers purpose, usage conditions, parameter guidance, and behavioral nuances, it is fully complete for an AI agent to use correctly.

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 adds meaning for 'confirmed' and 'sourceFolder' parameters, explaining their necessity and usage context. The schema already covers the other parameters (emailId, account_id) with adequate descriptions, so the additional value is moderate.

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 moves an email to Trash (not permanent deletion) and specifies behavior for already-trashed emails. This distinguishes it from sibling tools like empty_trash or permanent delete actions.

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 clear guidance on requiring 'confirmed: true' and passing 'sourceFolder' when UIDs come from non-INBOX folders. However, it does not explicitly differentiate from the sibling tool 'move_to_trash', which may cause confusion about when to use which.

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