Run a previewed bulk operation

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses crucial behaviors: the plan executes at most once, expires after 15 minutes, and the affected message set is immutable. This prevents an agent from retrying or modifying after the fact, which is not captured in annotations.

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?

Three sentences contain only high-value information with no repetition or filler. The core action is front-loaded, and critical constraints follow logically.

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 single-parameter destructive tool with annotations covering the safety profile, the description is nearly complete. It might benefit from noting what a successful execution returns, but this is minor given the low complexity and no output schema.

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 already documents plan_id with 100% coverage, but the description adds meaningful semantics: it is the only thing accepted, and the messages affected were frozen at preview time. This enriches the parameter beyond a simple schema declaration.

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?

States a specific verb ('Run') and resource ('bulk delete or move that was previewed as a plan'), clearly differentiating it from bulk_cancel or single-message deletes. The title and first sentence together make the tool's purpose unmistakable.

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?

Clearly indicates that execution follows a previewed plan and that the plan is frozen, so if an agent needs to change affected messages, this is not the tool. It does not explicitly name bulk_cancel or another alternative, but the constraint context strongly implies when to use it and the one-shot execution rule.

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