Delete Email

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

Annotations already indicate destructive and idempotent behavior. The description adds the specific behavioral detail that deletion is performed by moving to the Trash folder, which is not available from annotations alone. This provides useful context beyond what annotations state.

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 concise: a single sentence that immediately states the action and the required inputs. Every part earns its place without unnecessary 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 tool with two parameters and no output schema, the description is adequately complete. It explains the core behavior and parameter usage. However, it could mention success/failure behavior or error conditions to be 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?

The schema has 0% description coverage, so the description must add meaning. It maps 'folder name' and 'email UID' to the parameters uid and folder, but does not elaborate on format, ranges, or the fact that folder defaults to INBOX. The description provides basic semantic context but lacks detailed parameter guidance.

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 that the tool deletes an email by moving it to the Trash folder. It specifies the action (delete) and the resource (email), and it distinguishes itself from sibling tools like proton_list_emails or proton_move_email by explicitly mentioning moving to Trash.

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 some implicit guidance by stating the action is moving to Trash, which implies standard deletion. However, it does not explicitly compare to other tools like proton_move_email (which could also move to Trash) or explain when to use this versus a hard delete or other methods. No explicit when-to-use or when-not-to-use guidance is given.

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