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 context that it is a soft delete (moves to Deleted Items) and that a second delete results in permanent deletion. This goes beyond the annotation's binary flag.

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 consists of two short sentences, directly stating the action and providing a practical tip. No extraneous words, and the structure 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?

With 100% schema coverage and no output schema, the description covers the core action and behavioral nuance (soft vs permanent delete). It lacks explicit mention of prerequisites or error conditions, but given the simplicity, it is largely 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?

Input schema descriptions cover all 4 parameters, so baseline is 3. The description does not add extra meaning to any parameter beyond the schema.

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?

Clearly states the action ('Delete') and resource ('eventMessage'), which aligns with the tool name. However, 'eventMessage' is slightly ambiguous as it might refer to a specific subtype of mail messages, but it is still clear overall. The tool is distinct from other delete tools like delete-calendar or delete-mail-folder.

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?

Provides a clear tip about soft delete behavior and how to permanently delete, which guides the agent on the effect of the tool. However, it does not explicitly state when to use this tool over alternatives like delete-mail-attachment or delete-mail-folder, though those are distinct resources.

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