cve_search

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the search scope and filter but does not disclose how 'recent' is defined, default sorting, pagination, rate limits, or any other behavioral traits. The information provided is minimal and leaves key operational details undisclosed.

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, well-structured sentence that is front-loaded with the key action and resource. Every word adds value, and there is no unnecessary filler or repetition.

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 (3 params, a sibling tool, no annotations), the description covers the core purpose but omits usage differentiation with cve_lookup and important behavioral details. Since an output schema exists, return value explanation is not required, but for a search tool, more context about how results are limited or ordered would improve completeness.

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 description explicitly mentions keyword and minimum CVSS score, which adds meaning to two of the three parameters. However, the 'limit' parameter is not described, and with 0% schema description coverage, the description should more thoroughly explain all parameters. It partially compensates but leaves gaps.

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 tool searches the NVD for recent CVEs by keyword and filters by minimum CVSS score, with a specific verb ('Search') and resource ('NVD'). However, it does not explicitly differentiate from sibling tool cve_lookup, which may be used for retrieving a specific CVE by ID, so it misses some sibling differentiation.

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 implies the tool is for finding CVEs by keyword, but provides no explicit guidance on when to use it versus the sibling cve_lookup tool. It does not mention exclusions or prerequisites, relying on the user to infer usage from the wording.

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