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

Annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the mutation/idempotency profile is covered in structured data. The description adds the useful 'same answers' parity claim (same return shape as update_drop), but says nothing about what changes, permissions, or side effects on recipients' links. No contradiction with annotations.

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, front-loaded with the alias/routing fact that an agent needs first. The second sentence, the definition of a drop, is domain flavor rather than invocation guidance, but it is short enough to earn its place as context for the email/tracked-link model.

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?

A 13-parameter mutation tool with a 92%-covered schema and full annotations does not demand much prose, and no output schema exists so returns needn't be explained. However, the description never describes what an update actually does to the drop, leaving the alias pointer to carry the entire burden.

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 92%, so the 13 parameters are already well documented, including the campaignId note and the docId/projectId alternation. The description adds no parameter-level meaning at all; it only points to the sibling for argument behavior, which is the baseline expectation at this coverage level.

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 does the one thing that matters most for a name/title mismatch (tool is 'update_campaign' but titled 'Update drop'): it declares that this is lnkdrp_update_drop under its earlier name, with the same arguments and answers. That lets an agent route correctly by cross-referencing the sibling. It never states the specific verb+resource directly ('updates a drop's settings'), so it is one step removed from self-contained clarity.

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?

'Under its earlier name' is an implicit signal that this is the legacy alias, but there is no explicit rule for choosing between this tool and lnkdrp_update_drop when both are present. An agent facing both still has to guess which to call, and no when-not-to-use condition is given.

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