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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds value by listing the record's contents (CVSS, CWE, etc.) but does not disclose any behavioral traits beyond what annotations provide, such as authentication needs or rate limits. With strong annotations, a score of 3 is appropriate.

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: first states purpose and contents, second gives a concrete example. No wasted words, front-loaded with key information. Highly efficient.

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 existence of an output schema, the description does not need to detail return values. It lists the major fields present in the output, and the tool's simple input (single required parameter) makes it complete. Annotations further reduce the need for behavioral disclosure. Score 5 for 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?

Schema description coverage is 100% for cve_id, with a detailed format description. The description adds an example (CVE-2021-44228) and context, but this is marginal improvement over the schema. Baseline 3 is justified.

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 it fetches the canonical NVD record for a specific CVE-ID, listing key contents (description, CVSS, CWE, CPE, references). It distinguishes from sibling search tools by emphasizing specificity and 'canonical' record.

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 implicitly guides usage by focusing on a single CVE-ID and contrasting with the sibling nvd.cves.search tool (which would retrieve multiple). However, it lacks explicit when-to-use or when-not-to-use guidance, leaving some ambiguity for agents unfamiliar with NVD.

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