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

With no annotations, the description carries the disclosure burden itself. It usefully characterizes the output as 'bounded' evidence plus a change plan, hinting at scope limits, but says nothing about read-only behavior, data freshness/source, auth needs, or rate limits. The 'Get' verb implies a safe read, but this is inference rather than stated behavior.

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?

A single dense sentence with no filler. The required scope qualifier ('one exact CVE') and the payoff (change plan) are both front-loaded, so an agent can triage the tool at a glance.

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?

An output schema exists, so return values need not be re-explained, and the description still summarizes the payload. For a one-parameter read tool the coverage is nearly sufficient; the only meaningful gap is routing guidance against the other CVE-related siblings.

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% for the single 'cve' parameter. The description compensates partially by signaling that the value must be one exact CVE identifier (not a range or keyword), which adds real meaning over the bare schema, but it does not specify accepted formats such as CVE-YYYY-NNNN.

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 names a specific verb ('Get') and a tightly scoped resource ('one exact CVE'), then enumerates what is produced: evidence, recipe authority, and a bounded change plan. The word 'one exact' implicitly separates it from a multi-result sibling like recipes_cve_search, though no sibling is named explicitly.

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?

Usage is only implied. 'One exact CVE' suggests this is a single-item lookup rather than a search, but the description never states when to prefer it over recipes_cve_search, recipes_cve_catalog_info, or recipes_match_finding, nor does it give prerequisites.

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