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

Annotations already declare non-read-only, non-idempotent, non-destructive behavior, so the bar is lower. The description does contribute real domain context — a drop sends a template from the member's own Gmail to recipients and their contact lists with per-person tracked links — which tells the agent a duplicate spawns a sendable object with tracking. It omits what is and isn't copied and whether the copy is created as an unsent draft.

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: the alias relation is front-loaded, and the glossary sentence about what a drop is earns its place for an agent unfamiliar with the term. Slightly indirect phrasing ('the same answers') keeps it short of a 5.

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 mutation tool with annotations present, no output schema and full schema coverage, the missing pieces are what the duplicate contains (recipients, template, lists), whether the result is a draft, and any permission or confirmation requirement. Adequate to call it, not fully informative about the outcome.

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% (name default, 24-hex campaignId sourced from lnkdrp_list_drops, visibility semantics), so the schema carries parameter meaning fully. 'The same arguments' adds nothing beyond it, which is the correct baseline for a fully documented schema.

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 never states the operation in its own words ('duplicates a drop'); it defines the tool only by reference to lnkdrp_duplicate_drop. It does implicitly resolve the confusing campaign/drop split between the name and title, but the sentence is about the alias, not the action.

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_duplicate_drop, under its earlier name' names the equivalent sibling, but it never says when to use this one versus that one, whether one is deprecated, or what happens if the two diverge in the future. Usage is inferable (either alias is fine) rather than stated.

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