Search npm Packages

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds that the npm registry is the external source and that results include specific fields, but it does not disclose pagination, rate limits, or result ordering/caveats.

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 compact and well-structured: a purpose sentence, a usage sentence, and three illustrative examples. Every part adds value without redundancy, and the key information is front-loaded.

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 one-parameter search tool with strong annotations and a stated return shape, this is nearly complete. It could optionally mention pagination/limits or no-results handling, but the current description sufficiently enables correct selection and invocation.

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?

The single 'query' parameter is 100% covered by the schema, so the baseline is 3. The description's examples ('Search for Svelte authentication libraries') demonstrate full natural-language phrasing, complementing the schema's keyword-style examples and enriching how the agent should interpret 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 uses a specific verb ('Search') on a specific resource ('npm registry') and explicitly states the return fields (name, latest version, description). It also distinguishes itself by positioning as a precursor to depsonar_docs, setting it apart from sibling tools.

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?

Explicitly tells the agent when to use this tool ('find the right package name before calling depsonar_docs') and provides natural-language example queries. It does not enumerate exclusions or alternatives beyond depsonar_docs, but the context is clear enough for correct selection.

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