npm_unpublish_version

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

Annotations already flag destructiveHint=true, but the description adds critical detail: irreversibility, 72-hour block, and exact dist-tag behavior (auto-reassign only 'latest', others left unset). This goes well beyond the annotation's binary flag.

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 description is dense but each sentence carries unique weight—irreversibility, time window, safety mechanism, CLI flow, sibling distinction, and dist-tag side effects. No filler; well-structured with the core action first.

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 irreversible operation, this description is comprehensive: it explains consequences, constraints, side effects, and next steps. Absence of output schema is acceptable as no structured output is expected.

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 already covers all three parameters with descriptions, so baseline is 3. The description reinforces the confirm parameter's purpose but doesn't add new parameter semantics beyond the 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?

Clearly states it unpublishes a specific version of a package. Differentiates from sibling npm_unpublish_package by explicitly naming it as the alternative for full-package unpublish.

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?

Provides explicit guidance: only works within 72 hours, requires confirm=true, and for full-package unpublish use npm_unpublish_package. Also advises on reassigning dist-tags with npm_dist_tag_set after side effects.

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