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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no repetition. The description adds a genuinely non-obvious trait: affected products, packages and references are truncated to 25 with totals reported, which tells the agent results may be incomplete. Auth, rate limits, and not-found behavior are still unstated, keeping it below 5.

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, front-loaded with the core promise, followed immediately by the truncation caveat. The enumeration is dense but each item maps to a real payload category, so nothing is wasted.

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?

With no output schema, the description carries the burden of describing the return payload, and it does so by enumerating field groups plus the 25-item truncation rule. It stops short of covering error/not-found behavior and whether truncated lists can be retrieved in full, which an agent calling this would benefit from knowing.

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?

There is one parameter at 100% schema description coverage, with a regex pattern and an example already in the schema, so the baseline is 3. The description adds nothing about the id beyond that, but it also has no gap to compensate for.

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?

"Everything known about one CVE" states a specific verb-equivalent (retrieve full detail), a specific resource (a single CVE), and enumerates the payload categories (CVSS, CWE, KEV, EPSS, SSVC, affected products, references). It is clearly distinguishable from the sibling search_cves by being a single-record deep lookup.

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 CVE" plus a required id conveys a point lookup, and the enumerated scope hints this is the deep-detail call rather than a search. However, it never says when to use this instead of search_cves, nor states a prerequisite such as "you must already have a valid CVE id."

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