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 offers only the tagline 'what it is, what you get, what you pay' and 'free text or code,' which vaguely suggests a result list, but does not explain search semantics, return shape, read-only behavior, or any limitations. This is minimal behavioral information.

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 very short and front-loaded with the resource name. However, brevity crosses into under-specification: the tagline 'what it is, what you get, what you pay' is catchy but not informative enough to replace structured 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?

For a simple one-parameter search tool, the description is nearly complete on input but not on output or selection context. It lacks return-value semantics, how results relate to npm_get, and any search behavior details. Given the sibling get/search pattern, more context is needed for correct tool selection.

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 input schema has a single undocumented 'q' parameter with 0% description coverage, so the description's 'Free text or code' is the only clue to query semantics. It adds some meaning beyond the bare schema, but it omits examples, accepted formats, and whether q is a package name, keyword, or code fragment.

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 identifies the resource as 'npm / public packages' and hints that the query is 'free text or code,' which conveys the package-search domain. However, it never states an explicit verb such as 'search' or 'find,' and it does not differentiate this tool from the sibling npm_get. The purpose is inferable from the name but not clearly specified.

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 npm_search instead of npm_get or the many other *_search siblings. The description does not mention whether to use this tool for discovery before fetching details, nor any exclusion or alternative. An agent must infer usage from naming conventions.

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