Empty Spam

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

The description adds beyond the destructiveHint annotation by stating irreversibility, necessity of confirm:true, and the availability of dryRun:true, providing critical behavioral context.

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 concise sentences; first sentence clearly states purpose, second adds essential safety info. No wasted words, front-loaded.

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 simple destructive tool with good schema and annotations, the description adequately covers purpose, safety, and preview option. Could mention max parameter but schema covers it.

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?

Input schema has 100% description coverage, so baseline is 3. The description only implicitly references the query parameter and adds no new parameter-level details beyond the schema.

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 action ('PERMANENTLY delete everything in the Spam/Junk mailbox') and the ability to narrow by query, which is specific and distinct from sibling tools like empty_trash.

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 mentions irreversible nature, confirm requirement, and dryRun suggestion, but does not explicitly contrast with siblings (e.g., empty_trash) or provide when-to-use guidance.

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