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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context by enumerating what the response contains (CVSS scores, weakness IDs, references, affected products) and identifying NVD as the data source, which helps the agent anticipate the tool's output.

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 one tightly structured sentence that front-loads the operation, then supplies the ID format and the return fields. There is no filler, redundancy, or superfluous information.

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?

For a single-parameter read-only lookup with no output schema, the description provides the essential contract: the input format and a clear list of what will be returned. It is well differentiated from the many sibling tools and contains everything an agent needs to invoke it correctly.

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 coverage is 100% and the schema already provides an example, so the baseline is 3. The description adds a precise format contract 'CVE-YYYY-NNNN' that goes slightly beyond the schema's single example, giving the agent a more general rule for constructing valid identifiers.

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: 'Full detail for a single CVE by ID.' It also distinguishes the tool from siblings like cve_search_by_keyword and cve_recent by requiring a concrete CVE identifier and promising full detail rather than search results or recent lists, reinforced by the explicit ID format.

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 phrase 'by ID (format CVE-YYYY-NNNN)' makes clear the intended use: this tool is for looking up a single CVE when the identifier is known. However, it does not explicitly name alternatives or state when not to use this tool, so it provides clear context but no exclusions.

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