deleteEmail

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

With no annotations, the description carries the full burden and does the most important part: it explicitly states 'Permanently removes the email from the mail server,' which is the destructive semantics an agent must know. It omits auth/permission requirements, error behavior for invalid UIDs, and whether the UID is folder-scoped.

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 short, front-loaded sentences with zero filler. However, the second sentence could be folded in or expanded to add the missing usage context rather than just repeating the verb.

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 destructive two-parameter tool with no annotations and no output schema, the description covers the critical destructiveness but leaves gaps: no permissions, no error cases, no sibling routing. Adequate but clearly incomplete for a delete operation.

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?

Schema coverage is 0%, so the description should compensate, but it only restates that a UID identifies the email. It adds no clarity on whether the UID is IMAP message UID (which is folder-relative), and says nothing about the folder parameter or its INBOX default.

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?

Specific verb+resource ('Delete a specific email'), scoped by folder and UID, and clearly distinguished from siblings like moveEmail, markAsRead, and getEmailDetail. An agent can tell this is destructive deletion, not archival or flagging.

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 when-to-use guidance, no alternatives named, no preconditions. The description doesn't say to prefer moveEmail for recoverable operations or that this is irreversible, leaving the agent to infer context.

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