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

Annotations already declare destructive and idempotent, and the description adds substantial context beyond them: emails are re-sent one at a time a second or two apart from the owner's Gmail, a stopped drop becomes active again, confirmation is required regardless of connection settings, and the response contains the drop plus a 'retried' count. It also enumerates refusal codes with their details fields, which is unusually complete.

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?

Dense but almost every clause carries operational weight; the share of parenthetical interjections makes it slower to scan than it needs to be, and the one-sentence definition of a drop precedes the actual verb, so the purpose is not perfectly front-loaded.

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 destructive mutation with no output schema, the description covers authorization, async/rate behavior, state side effects, confirmation flow, return fields, and the full refusal taxonomy. An agent has everything it needs to call this correctly and to handle failures.

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 coverage is 100%, so the 3 baseline applies, but the description goes further by explaining the confirm/confirmationToken handshake with the preview and by tying memberIds to lnkdrp_get_drop. The 'every failed person' default is already in the schema, so that part adds nothing.

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 and resource: 'Sends the failed emails of a drop ... again', and defines what a drop is so the agent knows the object. It does not, however, distinguish itself from the near-identical sibling lnkdrp_retry_campaign_failed, despite noting a drop is 'a campaign in the API'.

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?

Gives clear preconditions and sourcing: the drop's owner must retry it, campaignId comes from lnkdrp_list_drops, memberIds from lnkdrp_get_drop, and a preview/confirm step is required every time. It never states when to prefer this over the campaign-level retry sibling, which is the main ambiguity left.

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