Delete Email

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

Adds behavioral details beyond annotations: email is moved to Trash and recoverable, no permanent deletion, leaves already-trashed emails in place. Annotations already mark destructiveHint true, so description adds useful safety 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?

Two sentences that are front-loaded with the main action and key constraints. No redundant information; every sentence earns its place.

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 output schema exists (not shown) and tool complexity is moderate, description covers behavior, required confirmation, and folder ambiguity. Could mention return type briefly, but output schema compensates.

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?

Adds meaning beyond schema: explains why sourceFolder is needed (IMAP UID scoping) and that confirmed must be true for execution. Schema already describes confirmed and sourceFolder, but description adds context.

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?

Description clearly states the tool deletes an email by moving it to Trash, clarifying it's never permanently deleted. This specific verb+resource distinguishes it from permanent deletion or other operations.

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 guidance on when to use (for deletion that moves to Trash), requires confirmed: true, and recommends sourceFolder for folder-scoped UIDs. Does not explicitly list alternatives or when not to use, but context from siblings like move_to_trash is clear.

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