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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so safety and repeatability are covered structurally. The description adds only the 'same answers' equivalence claim and never explains the effect of archiving (hidden from listings? revocable? does it affect a send in progress), so it contributes almost nothing behavioral.

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 first carries the actual identity information and is front-loaded, but the second is a lengthy domain gloss on what a drop is rather than on what archiving does, so it does not fully earn its space in an archive-tool definition.

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 two-parameter toggle with full schema coverage, a strong safety annotation set, and no output schema, the definition supplies the one thing structured fields cannot: that this is an alias of lnkdrp_archive_drop. The only real gap is that the alias/legacy-vs-canonical routing advice is left implicit.

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 both parameters (campaignId with the 24-hex pattern and its source tool, archived boolean with its default and true/false meaning) are fully documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does all the work.

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 action directly; it identifies the tool only by equivalence to lnkdrp_archive_drop ("same arguments and the same answers"), so the verb 'archive' is inferred from the name and sibling rather than asserted. It does clarify the domain object (a drop = one email template sent from the member's Gmail), which is useful, but an agent must consult another tool to learn what the operation actually does.

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?

No guidance on when to call this versus lnkdrp_archive_drop, its own twin, or restore_drop for reversal. The alias relationship implies the two are interchangeable but never says which is canonical or why an agent would pick one; nothing excludes misuse or states prerequisites.

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