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

With no annotations, the description carries the full burden. It does disclose a key side effect: deleting all stored emails. However, it does not mention irreversibility, required permissions, or what 'autonomous mode' entails. This is partial transparency, but a critical detail (permanent data loss) is implied rather than explicitly stated.

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 a single, well-structured sentence that front-loads the action and object. Every word earns its place — no fluff or redundancy.

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 one-parameter tool with no output schema and no annotations, the description is adequate but lacks context around 'autonomous mode' and any prerequisites or post-conditions. It fully explains the primary effect but leaves ambiguity about what makes this mailbox 'local' and whether the deletion is reversible.

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 100% — the only parameter 'address' is described in the schema. The description adds the qualifier 'local mailbox' but does not provide extra semantic value beyond the schema field description. Baseline 3 is appropriate.

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 uses a specific verb ('Delete') and a clear resource ('local mailbox') plus what is included ('all its stored emails'). It distinguishes itself from siblings like delete_email_account by specifying 'local' and 'autonomous mode', making the tool's purpose unambiguous.

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?

There is no guidance on when to use this tool versus the many sibling deletion tools (e.g., delete_email_account, delete_email_rule). The phrase 'autonomous mode' hints at a specific context but is not explained, and no alternatives or exclusions are mentioned.

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