check_cves

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

Description says 'check', implying read-only, but annotation destructiveHint=true indicates it may be destructive. This contradiction undermines transparency, and no further behavioral context is provided.

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?

Two concise sentences, the first explaining the core function and the second adding a key constraint (no API key). No wasted words.

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?

No output schema, and description does not explain what the tool returns or any side effects. The annotation contradiction adds confusion. Given low complexity, more detail on output and behavior is needed.

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?

Only one parameter 'path' is fully described in the schema (100% coverage). The description adds no extra meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Description clearly states the tool checks npm dependencies against the OSV vulnerability database, with a specific verb and resource. It differentiates from siblings like port_scan or supply_chain_audit by focusing on npm and stating no API key is needed.

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?

Description provides a clear use case (check npm dependencies) and mentions no API key is needed, but does not explicitly state when not to use or compare to alternatives like supply_chain_audit.

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