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

Annotations already declare destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuine consequence detail beyond that: queued newsletters and journey emails will actually go out to contacts again, which is the critical thing an agent needs before acting.

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, no filler, with the action front-loaded and the consequence following immediately. Every clause earns its place.

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-boolean mutation with a strong schema and annotations, the description supplies the missing 'what actually happens' context. It could still note the blast radius (all contacts on the marketing list) or irreversibility, but nothing essential is absent.

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 description coverage is 100% and the 'confirm' parameter is documented in detail in the schema itself (dry-run semantics, pass true only after approval). The description adds nothing about parameters, so the baseline 3 for full schema coverage applies.

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+resource pair ('Lift a pause on marketing email') and clarifies the resource scope, distinguishing it from the similarly named resume_journey sibling. An agent knows exactly which switch this flips.

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 parenthetical explains the typical trigger ('set after high bounces or complaints'), which implies when the tool is relevant, but it never states when to prefer this over resume_journey or pause_proactive_message, nor any precondition for flipping the switch. Usage is inferable but not routed.

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