npmVulnerabilities

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

Annotations already declare readOnlyHint=true (safe read operation), openWorldHint=true (can handle unknown packages), and idempotentHint=false (results may vary). The description adds that it checks 'known vulnerabilities,' which implies it queries an external database (likely OSV.dev as hinted in the title annotation), but doesn't disclose rate limits, data sources, or response format. With annotations covering key traits, this adds some context but not rich behavioral details.

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, efficient sentence that directly states the tool's function without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 moderate complexity (checking vulnerabilities), annotations provide safety and scope hints, but there's no output schema to explain return values. The description is minimal and doesn't cover aspects like error handling or what constitutes a 'vulnerability,' leaving gaps that could hinder effective use by an 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 description coverage is 100%, with the parameter 'packages' clearly documented as 'List of package names to check for vulnerabilities.' The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 verb ('Check for') and resource ('known vulnerabilities in packages'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'npmQuality' or 'npmScore' that might also assess package safety aspects, so it doesn't reach the highest score.

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. With siblings like 'npmQuality' and 'npmScore' that might overlap in safety assessment, there's no indication of when vulnerability checking is preferred over other metrics or what specific context warrants its use.

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