NPM Package Documentation

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

With no annotations, the description carries the full burden of disclosing behavior. It fails to mention whether the tool fetches live data, returns static text, requires network access, or has side effects. The description is completely silent on any behavioral traits.

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 extremely brief, but brevity here is under-specification rather than conciseness. It does not front-load useful information; the single sentence is too vague to help an agent understand purpose or usage, so it does not earn its place as meaningful guidance.

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 simple tool (one parameter), the description still fails to convey what output or result the agent should expect. With no output schema present, the description must explain return values, but it does not. This makes the tool effectively opaque.

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%: the only parameter, 'packageName', is fully described as 'The name of the npm package to get documentation for.' The tool description adds nothing extra, but the baseline for high schema coverage is 3, and the schema already provides adequate semantic clarity for the parameter.

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 'Documentation for the npm package.' essentially restates the tool name and title without specifying an action (e.g., retrieve, fetch, list). It does not distinguish the tool from any other potential npm-related utilities, making it a tautological rather than informative explanation.

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?

There is no guidance on when to use this tool, what problem it solves, or any alternatives. Since no sibling tools or context are provided, the description gives no indication of appropriate usage scenarios, leaving the agent without direction.

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