delete_email

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

The description only states the action (move to Trash) without disclosing behavioral traits such as whether the operation is reversible, requires permissions, or affects attachments. Since no annotations are provided, the description carries full burden but provides minimal disclosure.

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?

A single sentence with 12 words, front-loaded with the action. Every word is necessary and clear. No redundancy.

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 tool with two parameters and an output schema, the description is adequate but lacks behavioral context (e.g., irreversibility). It does not leverage the output schema to explain return values.

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?

Input schema has 100% coverage, so baseline is 3. The description adds no new information beyond schema: it restates 'by its IMAP message ID' and does not clarify parameter formats or constraints.

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 uses a specific verb+resource pair ('Move an email to the Trash folder') and specifies the method (IMAP message ID). It clearly distinguishes from sibling tools like 'delete_all_in_folder' which handles bulk deletion.

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 implies when to use (when you have an IMAP message ID) but does not provide explicit guidance on when not to use or mention alternatives like 'delete_all_in_folder' or 'move_email'.

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