delete_email

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

The description discloses that deletion is actually a move to Trash unless expunge=True or already in Trash, adding important behavioral context beyond annotations (destructiveHint, idempotentHint). 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 a single, concise sentence that communicates the core behavior and key caveats with no wasted words.

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 three-parameter tool with an output schema, the description covers the essential behavior (trashing vs. permanent delete) and context. No additional details are needed.

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 basic parameter descriptions. The tool description does not add additional meaning beyond what is already in the schema, but also does not repeat it unnecessarily.

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 deletes an email, with the key nuance of moving to Trash unless expunge=True or already in Trash. This differentiates it from siblings like move_email or delete_folder, which have different 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?

The description explains the conditional behavior (move to Trash vs. permanent delete), providing context for when to set expunge. However, it does not explicitly contrast with alternative tools like move_email or when not to use this tool.

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