cve_search

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

Discloses that results are sorted by CVSS base score (descending). However, no annotations exist, and the description does not mention rate limits, pagination, or response format, leaving gaps in behavioral understanding.

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 sentences with zero waste. Front-loaded with verb, resource, and example, making it immediately actionable.

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?

Covers core purpose and sorting behavior but lacks explanation of return fields, pagination, or result format. For a search tool with no output schema, this is a gap. Sibling tools like cve_lookup hint at additional functionality but not described.

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 has two parameters (keyword, limit) with 0% description coverage. Description only illustrates 'keyword' via example and does not explain 'limit' or its default, failing to add significant meaning beyond the schema.

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 'Keyword-search the NVD for CVEs' with a concrete example, distinguishing it from siblings like cve_lookup (direct lookup) and vuln_scan (broader scanning).

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?

Explicitly says 'Use this to map a fingerprinted product/version to known vulnerabilities', providing clear context. Does not explicitly state when not to use or mention alternatives, but sibling tool cve_lookup implies a different use case.

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