delete_email

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

Annotations include destructiveHint: true, and the description adds behavioral context: soft-delete by default and the existence of a permanent parameter. This clarifies the degree of destruction beyond the annotation, though it does not mention behavior for already-deleted emails or recovery options.

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, no fluff. First sentence states the core purpose; second adds a critical behavior detail. Well-front-loaded and efficient.

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 5 parameters and low schema coverage, the description only marginally covers the tool's behavior. It explains the delete mechanism but omits details on required parameter uid, optional folders, and output. While output schema exists, the description could still benefit from noting that the tool has a return value.

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 schema description coverage at only 20%, the description adds meaning for the permanent parameter by explaining its effect. However, it provides no explanation for uid, folder, account, or trash_folder, leaving several parameters without semantic context. The description partially compensates but not fully.

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 clearly states the verb 'Delete' and resource 'message', and distinguishes soft-delete (moves to Trash) from permanent deletion. This differentiates it from sibling tools like move_email and delete_folder.

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 implies usage for deleting emails but does not provide explicit guidance on when to use vs alternatives (e.g., move_email for organizing), nor does it give when-not-to-use scenarios. The context of soft-delete is stated but not compared to permanent deletion.

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