delete_email

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It fails to mention whether deletion is permanent or moves to trash, whether it affects only the current folder, or what happens to associated attachments. The bare statement 'Delete email(s)' offers no behavioral context beyond the action itself.

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 extremely brief, but it is under-specification rather than efficient conciseness. It lacks critical context that a delete operation requires, so the brevity is not a positive attribute.

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 operation with no annotations and no output schema, the description is woefully incomplete. It does not specify whether deletion is hard or soft, how UIDs are scoped, or any side effects. The simple parameter count does not excuse this lack of essential operational context.

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 description coverage is 100% (the only parameter 'uids' has a description 'Email UIDs'). The tool description adds no extra meaning about the parameter, but the baseline is 3 given high schema coverage.

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 'Delete email(s)' is a direct restatement of the tool name 'delete_email', adding only a plural marker. It does not provide any distinguishing information beyond what the name already conveys, making it essentially a tautology.

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 like move_email or mark_read. There is no context about prerequisites, folder selection, or distinguishing from other email operations.

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