confirm_batch_operation

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

With no annotations, the description carries the full behavioral disclosure. It details return format (per-email results, summary with counts) and partial failure behavior (invalid, expired, or used tokens fail without blocking others). This goes beyond typical descriptions and is highly informative.

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 four concise sentences, each with a clear purpose: purpose, selective usage, return value, and partial failure behavior. It is front-loaded with the main action and contains 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?

Given no annotations and no output schema, the description provides sufficient detail on execution, return values, and error handling. It references the specific prepare tools and allows an agent to invoke the tool correctly without additional information.

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 the schema already documents the tokens array. The description adds meaning by explaining the tokens come from prepare_batch* steps and that selective confirmation is possible by including only desired token/email pairs. This adds context 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 confirms and executes a batch operation, specifically using tokens from prepare_batch_delete_emails or prepare_batch_move_emails. This distinguishes it from single-email confirm tools and clearly specifies the resource and verb.

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 explicitly indicates when to use the tool (after prepare_batch* tools) and introduces selective confirmation, but does not explicitly mention alternatives (e.g., single confirm tools) or state when not to use it. This is still clear, but lacks a direct exclusion.

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