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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, so the description only needs to add side-effect detail. It mentions 'fresh' but never states that an email is actually dispatched, whether the previous confirmation link is invalidated, or what happens if the recipient is already confirmed — the highest-value context for a non-idempotent mutation.

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?

A single front-loaded sentence with zero filler; the core action and target states come first. It is arguably over-economical for a non-idempotent write with two required IDs, leaving no room for the qualifiers the other dimensions need.

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 two required opaque IDs, no output schema, and zero parameter documentation, the description should carry more weight than one sentence. Missing are preconditions (recipient must exist and be unconfirmed), error cases, and whether the operation triggers an external email — all things annotations cannot supply.

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 0%, so both required parameters (websiteId, recipientId) are undocumented in the schema and the description compensates for neither. It doesn't say that recipientId must belong to the given website or what an invalid pair returns, leaving the agent to guess from parameter names alone.

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+object ('issues a fresh confirmation link') and scopes it to recipients in particular states, which is clearly distinct from websiteForms_recipients_add/remove. It never names those siblings or clarifies that this is a re-send for an existing recipient rather than a new invitation, so an agent must infer the distinction from the tool name alone.

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 phrase 'pending, failing, or stopped address' gives a concrete usage condition tied to recipient status, so an agent knows this is for unconfirmed/stalled recipients rather than fresh ones. No exclusions or explicit routing to add/remove alternatives are given, which keeps it out of 5 territory.

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