delete-mail-message

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

Annotations already indicate destructiveHint: true, but the description adds valuable detail: 'Soft delete — moves to Deleted Items. To permanently delete, delete again from Deleted Items.' This exceeds the annotation and clearly discloses behavior.

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 extremely concise: a single sentence plus a tip. Every word adds value, and the tip is front-loaded.

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 delete operation with destructiveHint annotated, the description provides complete context: the action, the soft delete nuance, and how to permanently delete. No output schema is needed given the simplicity.

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 coverage is 100% (all 5 parameters have descriptions). The description does not add further parameter details beyond the schema, so it meets the baseline of 3.

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 'Delete eventMessage' using a specific verb and resource. The tip distinguishes soft delete behavior from permanent delete, and the tool is clearly differentiated from sibling tools like 'move-mail-message' and 'delete-mail-attachment'.

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 tip explains that this is a soft delete and how to permanently delete, providing context. While it doesn't explicitly state when not to use this tool or list alternatives, the context is sufficient for an agent to gauge usage.

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