execute_decisions

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

Beyond annotations indicating destructiveness, it details exact effects (archive moves, delete recovers, unsubscribe follows RFC 8058), safety thresholds, and domains never touched.

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?

Information is front-loaded and structured by decision type, but slightly dense; bullet points could improve scannability.

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 main behaviors and constraints well, but omits details on error handling and exact safety threshold values.

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?

With 0% schema coverage, the description fully explains account necessity, decision values (archive/delete/unsubscribe), and confirm_token conditions and source.

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 executes tagged decisions with specific actions (archive, delete, unsubscribe), and distinguishes itself as 'THE ONLY DESTRUCTIVE TOOL' among siblings.

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?

It explicitly notes when confirm_token is needed and ties to preview_cleanup, but doesn't explicitly compare to non-destructive siblings like set_decisions or preview_cleanup.

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