npmQuality

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

Annotations already indicate readOnlyHint, idempotentHint, and openWorldHint, which cover safety and repeatability. The description adds no behavioral context beyond 'analyze', which is consistent but not enriching. No contradictions.

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 concise at 6 words, clearly stating the core functionality without waste. However, it could be slightly expanded to include context like the source (NPMS.io) without losing conciseness.

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 has 2 parameters with full schema descriptions and annotations covering safety, the minimal description suffices for a read-only analysis tool. However, it lacks details about output format or what 'quality metrics' entails, leaving some ambiguity for the agent.

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 100% with descriptions for both parameters. The description adds no extra meaning beyond the schema, but the baseline of 3 is appropriate as the schema sufficiently documents parameter semantics.

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 'Analyze package quality metrics' clearly states the verb (analyze) and resource (package quality metrics). It is distinct from the sibling tool 'npmLicenseCompatibility' which focuses on licenses, but it does not explicitly differentiate. Could be more specific about the metrics involved.

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?

The description provides no guidance on when to use this tool versus alternatives, such as comparing with npmLicenseCompatibility. It lacks information on prerequisites or use cases, forcing the agent to infer from context.

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