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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description is a mere noun phrase and reveals nothing about return format, authentication requirements, rate limits, or side effects. There is no information about what the tool actually does beyond the label.

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 short, but it is under-specified rather than concise. It is a fragment without a verb or structured information. It does not front-load any actionable details; it simply restates the tool name in a descriptive phrase.

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 single optional parameter, no annotations, and no output schema details provided, the description is severely incomplete. An agent cannot correctly invoke this tool without knowing what value to pass to 'q' or what to expect in return. The description fails to provide any of the needed context.

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 one parameter 'q' with no description and 0% schema description coverage. The tool description does not mention this parameter at all, leaving its purpose and format entirely unexplained. The agent cannot know whether 'q' is an organization name, a search term, or something else.

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 states 'npm Org: npm organization: all published packages' which indicates the resource (npm organization) and scope (all published packages), but lacks a clear verb or explicit action. It is not tautological, but it is ambiguous about whether it lists packages for an organization or returns organization metadata. It does distinguish from a specific package lookup like npmpkg, but only loosely.

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 on when to use this tool versus alternatives. With many npm-related siblings (npm, npmpkg, npmdl, npmdownloads), the description does not explain the selection criteria or any exclusions. The agent must infer usage from the name alone.

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