Empty Trash

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

Discloses permanent deletion and irreversibility beyond the destructiveHint annotation. Also mentions the dryRun safety mechanism and the need for confirmation, adding full transparency.

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 succinct sentences front-load the main action and then cover safety caveats. Every word earns its place; no filler.

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?

Covers the core behavior, preview, and confirmation. While no output schema exists, the description could explicitly mention what the tool returns on success (e.g., count or status). However, the parameter descriptions hint at return values via 'done:false'.

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 significant value beyond the 100% schema coverage. Explains the purpose of confirm (required for destructive/large batches), dryRun (preview count/sample), and max (cap, timeout handling with done:false).

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 names the resource ('Trash mailbox'), with optional narrowing by query. It clearly distinguishes from siblings like 'empty_spam' and 'trash_message'.

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?

Explicitly states that the action is irreversible and requires confirm:true, and recommends using dryRun:true for preview. Provides clear when-to-use and when-not-to-use guidance.

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