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

No annotations are provided, so the description carries the behavioral burden. It discloses the CVE severity scope and signals that this tool does not return complete details. It does not mention result limits, pagination, ordering, or how filters like kev_only and published_year affect the search.

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 compact sentence with no filler. The core scope is front-loaded and the pointer to recipes_cve_get is delivered in an efficient clause.

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?

The description gives a clear high-level purpose and useful sibling routing, and the output schema can cover return shape. However, with five parameters, zero annotations, and no parameter semantics, the agent is left to infer too much about query behavior, filter combinations, and the meaning of 'in-scope'.

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 0%, yet none of the five parameters (query, limit, kev_only, severity, published_year) is explained in the description. The phrase 'Medium/High/Critical' hints at severity scope but does not clarify parameter formats, defaults, or query behavior.

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 states a specific verb and resource: 'Search every in-scope Medium/High/Critical CVE'. It also distinguishes itself from recipes_cve_get by pointing there for 'complete details', so an agent can tell search from detail lookup without opening schemas.

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?

It names the sibling recipes_cve_get as the place for complete details, giving clear routing guidance for when richer output is needed. It does not explicitly state when not to use this tool, but the alternative is identified clearly.

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