email_cleanup

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

The description mentions returning actions for review before committing, hinting at a dry-run mode. However, it does not explicitly explain how to execute the actual cleanup (setting dry_run=false) or clarify that it archives rather than deletes emails.

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, front-loaded with purpose. No wasted words, though 'organizing' is vague. Concise overall.

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?

Missing details on how to commit the cleanup (dry_run=false), no description of return format, and vague 'organizing' action. Incomplete for a tool with no output schema and many siblings.

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%, so baseline is 3. The description adds marginal value by linking 'archive old emails' and 'removing newsletters' to parameters, but does not explain 'organizing' or add nuance 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 tool's purpose: archiving old emails, removing newsletters, and organizing. It distinguishes itself from single-action siblings like email_archive by being a batch cleanup operation.

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?

No guidance on when to use this tool versus alternatives (e.g., email_archive, email_trash) or when not to use it. Missing context about prerequisites or typical scenarios.

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