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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: emails go out from the member's own Gmail to recipients with individually tracked links, which conveys the external side effect. It stops short of saying the send is irreversible or that a preview confirmation is required before it fires.

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, with the alias relationship front-loaded so the agent immediately knows what it is looking at. The second sentence is long but carries genuine domain meaning rather than filler; nothing is redundant.

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, open-world send operation with no output schema, the description covers what a drop is and that this is a naming alias, and annotations carry the safety hints. It leaves out the preview/confirm handshake that the schema's confirm and confirmationToken parameters imply, and gives no guidance on preferring lnkdrp_send_drop.

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 all three parameters — confirm, campaignId with its 24-hex pattern and source, and confirmationToken — are documented in the schema. The description only says 'the same arguments,' adding no syntax or constraint detail, so the baseline 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 this is the earlier-named twin of lnkdrp_send_drop with the same arguments and answers, and then defines what a drop actually is (one email template sent from the member's own Gmail to chosen people and contact lists, each with a tracked link). The verb is conveyed by reference to the sibling rather than stated directly, but the domain object is explained well enough to distinguish it from create_drop, dry_run_drop, and send_email.

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?

'Same as lnkdrp_send_drop, under its earlier name' tells the agent the two are interchangeable, which is useful routing information. However, it never says which name to prefer, whether this one is deprecated, or when to choose it over the sibling — the agent must infer the alias relationship from the phrase 'earlier name'.

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