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

Beyond the annotations it discloses the full conditional state machine: review-before-send by default, direct queueing only when the 'Let Claude send without review' setting is on, and returned queued/suppressed counts. The claim 'safe to call again; it never re-sends' sits slightly at odds with idempotentHint=false, though it is a safety nuance rather than a core-semantic conflict.

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?

Purpose and return contract are front-loaded, then conditional agent instructions follow in a single dense paragraph. Every sentence earns its place, though bullet-structuring of the status branches would read more cleanly.

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?

With no output schema, the description fully specifies return states (ready_for_review with review_url, approved, queued/suppressed) and the required agent response for each. An agent has everything needed to call and act on the result.

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?

There is a single parameter (campaign_id) with 100% schema description coverage, so the schema already carries the semantics. The description adds no format, source, or lookup guidance for campaign_id, so the baseline of 3 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?

The description states a precise verb+resource and outcome: 'Tell RankParse a campaign's emails are ready' returning ready_for_review with a review_url. The launch action is clearly distinct from create/pause/resume siblings, but the description never names or contrasts a sibling, so it stays at 4.

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 gives explicit when-to-call ('only call it after the user has seen the drafted emails and explicitly approved sending') and when-not-to-call ('If status is approved, it is already approved; do not launch again'). It also routes the agent's follow-up behavior by return status, leaving nothing to inference.

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