npmVersions

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint. The description adds that it fetches all available versions, but does not elaborate on caching behavior, rate limits, or output structure. Since annotations cover safety and idempotency, the description adds moderate value.

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?

One sentence, no fluff, front-loaded with purpose. Every word earns its place. Perfectly concise for the information it conveys.

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 tool with 2 params and no output schema, the description is adequate but lacks mention of the array nature of 'packages' and the semantic of 'ignoreCache' (though schema describes it). Could be improved by noting that it returns versions for multiple packages at once. Not fully complete but acceptable.

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 coverage is 100%, so baseline 3. The description does not add any parameter-specific meaning beyond what the schema already provides for 'packages' and 'ignoreCache'. No extra semantics.

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 'Get all available versions of an NPM package' uses a specific verb ('Get') and resource ('all available versions of an NPM package'). It clearly distinguishes from siblings like npmLatest, npmSearch, etc. Minor mismatch: accepts multiple packages but says 'an NPM package', but still clear.

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 use this tool vs alternatives like npmLatest or npmDeps. No when-not-to or explicit context. The description lacks any usage recommendations.

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