Delete Email

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

Because no annotations are provided, the description carries the full behavioral disclosure burden. It does disclose an important non-obvious behavior: deletion is implemented as moving to Trash, not permanent destruction. However, it does not mention side effects, permission requirements, or how the optional folder parameter affects the operation.

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 a single short sentence that front-loads the action and then adds the essential qualifier about Trash. There is no redundant wording or unnecessary detail, so every word 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?

For a simple two-parameter mutation with no output schema, the description plus fully documented schema parameters are nearly sufficient. The main omissions are any statement about what the API returns and whether the delete can be reversed, though 'move to Trash' reasonably implies recoverability.

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 100%, with 'Message UID' and 'Source folder' already documented. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 identifies the verb ('Delete') and the resource ('an email'), and the parenthetical 'move to Trash folder' clarifies the exact semantic outcome. This distinguishes it from permanently erasing a message and from sibling operations like move_email or delete_draft.

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?

There is no guidance about when to use this tool versus alternatives. With siblings like move_email and delete_draft present, an agent gets no explicit cue about which tool is appropriate or when this tool should not be used.

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