Email Delete

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

The description elaborates on the annotations by explaining that the default behavior is a soft delete (move to Trash) while setting permanent to true causes permanent deletion. This adds meaningful nuance beyond the destructiveHint and readOnlyHint annotations, though it could further note irreversibility of permanent deletion.

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 sentence that directly states the core behavior and both operational modes. Every word contributes meaning, with no filler or repetition of schema content.

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?

The schema fully documents the parameters, and the description explains the primary behavioral choice. Given the output schema exists and annotations already mark the operation as destructive, the description is sufficient for an agent to invoke the tool correctly, though a brief note on permanent-deletion irreversibility would make it fully complete.

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%, so all parameters are already documented in the input schema. The description itself adds no new parameter-level detail; it only reiterates the behavioral distinction between permanent and non-permanent deletion, which the schema already captures.

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 names a specific action ('Move a message to Trash, or delete it permanently') and a clear resource ('a message'). It also distinguishes between soft and hard delete, which separates it from sibling tools like email_move, making the tool's purpose immediately understandable.

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 clearly states the two modes of operation: moving to Trash by default or permanent deletion when requested. It does not explicitly mention alternative tools or when not to use it, but the context is clear enough for an agent to choose this tool for deletion-related tasks.

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