batch_email_action

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

Provides details beyond destructiveHint annotation, including the 'dryRun' preview, the requirement of 'targetFolder' for move, and a caution on delete being a permanent expunge.

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 meaningful sentences plus an enumeration of actions; no filler, front-loaded with core purpose. Highly 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?

Covers purpose, action list, key parameter constraints, dryRun, error handling default, and alternative tool. Complete given schema and annotations.

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 80%; description adds context for 'dryRun' and action-specific requirements (move needs targetFolder, restore defaults to INBOX). Slightly above baseline.

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-resource combination ('Apply a mailbox action to multiple emails') and distinguishes sibling tool 'apply_thread_action' by noting it works on threadId.

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 recommends alternative tool 'apply_thread_action' for thread-based actions and warns about the delete action being permanent, guiding appropriate usage.

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