delete_email

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It fails to explain whether deletion is irreversible, moves to trash, requires special permissions, or has any side effects. A destructive action needs significantly more behavioral context.

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 short with a clear header and structured Args block. No wasted words, but the Args section could be integrated into the main sentence for even tighter prose.

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?

Given no annotations and three required parameters, the description omits important context: it does not mention the return value (output schema exists but is unaddressed), error conditions, idempotency, or prerequisites. A deletion tool should disclose the outcome or confirmation.

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?

With 0% schema description coverage, the Args section adds meaning by naming what each parameter represents and giving an example for account (e.g., 'work', 'personal'). However, it does not provide additional constraints, formats, or range information 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?

The description explicitly states 'Delete an email by UID,' using a specific verb (delete) and resource (email) with the method (by UID). This clearly distinguishes it from sibling tools like get_email, list_emails, move_email, and send_email.

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 no guidance on when to use this tool versus alternatives, such as whether deletion is permanent or if there is a trash/purge workflow. It only states the action without any contextual cues or exclusions.

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