delete_email

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that deletion does not permanently purge but 'moves to Deleted Items', which is a key behavioral nuance beyond the raw action. It does not mention permissions, error conditions, or side effects, but for a simple delete operation, this level of disclosure is valuable and largely sufficient.

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 front-loads the action and adds a crucial qualifier. Every word earns its place; there is no fluff or 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 tool with one parameter and no output schema, the description provides the essential behavior (delete and move to Deleted Items). It does not explain return values or success/failure outcomes, but for a simple delete action, the description is adequately complete given the low complexity.

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 description for messageId ('Message ID') fully covers the parameter. The tool description adds no additional meaning to the parameter beyond identifying it as the message to delete. Since schema coverage is 100%, the baseline of 3 applies.

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 states the action ('Delete a message') with a specific resource and clarifies the behavior ('moves to Deleted Items'), distinguishing it from permanent deletion and from sibling tools like move_email. The verb and object are clear and the scope is precise.

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 usage is implied by the name and description—use this tool to delete an email. However, there is no explicit guidance on when to use it over alternatives (e.g., move_email to Deleted Items, or update_email to change flags) and no mention of prerequisites or exclusions. The guidance is minimal but not misleading.

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