open-context_get_npm_info

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

The description mentions caching ('Fetch and cache'), which indicates a behavioral trait beyond a simple fetch. However, it does not explain caching details (e.g., duration, storage), network requirements, rate limits, or authentication needs. No annotations are provided to cover these aspects.

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 a single concise sentence with no wasted words. It is front-loaded with the main action. While very brief, it covers the core purpose without extraneous details. Could benefit from slight expansion for completeness, but conciseness is strong.

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?

There is no output schema, so the description should clarify what information is returned. It only states 'information about npm packages' without specifying the structure or content (e.g., version, dependencies, metadata). Given the complexity of npm package info, this is a significant gap.

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% with both parameters having descriptions. The tool description adds the concept of caching but does not provide additional parameter-level semantics beyond what is already in the schema. Baseline score of 3 is appropriate as schema does the heavy lifting.

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 'Fetch and cache information about npm packages from the npm registry' uses a specific verb (Fetch and cache) and specifies the resource (npm packages from npm registry). It clearly distinguishes from siblings focused on other ecosystems (e.g., Docker, Ansible).

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?

The description does not explicitly state when to use this tool versus alternatives. However, the intended use is implied by the tool name and sibling context, as it is clearly for npm packages while siblings cover other ecosystems. No explicit when-not-to-use or alternative naming is provided.

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