search_npm

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

No annotations are provided, so the description must carry the full burden of disclosure. It only says 'Search' and offers no details about result format, pagination behavior, default sorting, or any side effects. This is not a contradiction, but it is minimal and leaves much to inference.

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, front-loaded sentence with no filler. Every word contributes to communicating the core purpose, making it highly efficient.

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 tool's complexity (4 parameters, a nested weights object, no output schema), the description is far too sparse. It omits pagination semantics, weight interpretation, and response shape, so an agent cannot confidently invoke this tool without additional information.

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 only 25%, with descriptions provided solely for 'query'. The description does not add any meaning for 'from', 'size', or the nested 'weights' object. It fails to compensate for the low schema coverage, leaving those parameters semantically opaque.

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 clearly states the tool's function: 'Search the npm registry for packages.' The verb 'Search', resource 'npm registry', and object 'packages' make it specific and easy to distinguish from siblings like get_readme or get_package_info.

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 is provided about when to use this tool versus alternatives. In particular, there is a near-identical sibling tool 'search_by_keywords' that likely overlaps in functionality, and the description does not clarify which search tool to select for a given task.

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