delete_email

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

The description declares permanent deletion but omits critical behavioral details such as lack of undo, required permissions, or confirmation steps. With no annotations available, the description alone is insufficient.

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 with no extraneous words. While concise, it could be slightly expanded to include behavioral hints without sacrificing brevity.

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, single-parameter destructive tool without output schema, the description partially covers the required context (permanence of deletion). However, it lacks details like limitations or side effects, leaving room for improvement.

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 input schema has 100% description coverage, specifying 'messageId' as 'Email message ID to delete'. The description adds no new meaning beyond the parameter name and schema, achieving baseline adequacy.

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 "Permanently delete an email" clearly states the action (delete) and the resource (email), distinguishing it from sibling tools like 'batch_delete_emails' (multiple deletion) and 'remove_label' (non-deletion action).

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?

No context is provided on when to use this tool versus alternatives (e.g., batch_delete_emails), nor any prerequisites, caveats, or instructions for proper usage.

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