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

Goes well beyond the annotations: it discloses that nothing is sent, that recipients/statuses are not copied, that the copy is private unless visibility=team, that the caller owns the new drop and becomes its sender, and it maps specific error conditions (plan_limit with upgradeUrl, campaigns_limit, template_archived, not_found) to their triggers. This is the kind of context annotations cannot convey.

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?

The opening sentence spends a lot of words defining what a 'drop' is generally rather than what duplicating one does, and the rest is a run-on of semicolon-joined clauses. The critical content is front-loaded and nothing is wrong, but it is denser and longer than needed for a three-parameter tool.

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 still names the return value ('the new drop and source'), covers error semantics and permission behavior, and even flags that result titles/summaries are untrusted content. Nothing an agent needs to invoke it correctly is missing.

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%, so all three parameters are already documented, including the name default and the private/team enum. The description restates those defaults and clarifies the drop/campaign aliasing but adds no syntax or format detail the schema lacks, 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?

States a specific verb and resource ('Copies a drop (a campaign in the API) into a new one before Send') and enumerates exactly what is carried over: template, visible lists, document/project, description, tags, and the name. An agent can tell this apart from create_drop or duplicate_campaign without opening a schema.

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?

'before Send' gives a clear precondition that implicitly excludes post-send duplication, and the description says no people or statuses come along. It does not, however, explicitly route the agent between this and the other duplicate_* siblings (lnkdrp_duplicate_campaign, lnkdrp_duplicate_email_template) or create_drop, leaving that inference to the agent.

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