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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not state what happens if no version satisfies the range (e.g., returns null or throws), nor any side effects or permissions. The npm-style hint is useful but insufficient for full transparency.

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?

A single sentence with 10 words, front-loading the core purpose. Every word is necessary, and no redundant information is present.

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?

Given the low complexity (2 simple params, no output schema), the description is mostly adequate. However, it fails to indicate the return value (string version or null) and does not mention edge cases like invalid range or empty versions list.

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 0%, so the description must compensate. It adds the semantic detail that the range is 'npm-style', which clarifies the expected format. However, it does not describe the 'versions' array beyond the schema definition, leaving the full burden on parameter names.

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 uses a specific verb ('pick') and identifies the resource ('highest version') with the constraint ('satisfies a semver range'). It clearly distinguishes from sibling tools like semver_satisfies (checks boolean) and semver_sort (orders versions). The phrase '(npm-style)' further clarifies the semver variant.

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 explicit guidance on when to use this tool versus alternatives like semver_satisfies_batch or semver_compare. The usage is implied by the tool's name and description, but there is no 'when to use' or 'when not to use' advice.

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