List npm package versions

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds 'newest first' and the inclusion of dist-tags, which are useful behavioral details, but does not disclose potential edge cases (e.g., registryUrl behavior, error conditions). This matches the baseline for a well-annotated read-only tool.

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 core action, and every clause carries meaning. There is no redundancy or filler.

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 simple read-only listing tool with strong annotations, a complete parameter schema, and an output schema (present but not shown), the description is sufficient. It explains the primary use case and the result ordering, while the schema and annotations cover the remainder.

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 the schema fully documents all three parameters. The description does not add parameter-level detail beyond what the schema provides; it only reinforces the 'newest first' ordering already mentioned in the limit parameter's description. Baseline 3 is appropriate.

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 states a specific verb ('List') and resource ('published version numbers and dist-tags for a package from the npm registry'), and adds the 'newest first' ordering. It also signals the sibling relationship by noting this is useful before requesting metadata, distinguishing it from get_npm_package_metadata.

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 clear context: 'Useful for checking what versions exist before requesting metadata for a specific one.' This implies when to use the tool versus fetching metadata, though it does not explicitly name the sibling or state exclusions. It is sufficient guidance without being overly prescriptive.

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