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

Annotations already declare readOnlyHint and idempotentHint, and the description adds useful non-obvious behavior: no key is required over MCP, an API key is honored only for attribution, and null fields carry a specific absence semantic. This goes well beyond the annotation metadata without contradicting it.

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 dense paragraph, but it front-loads the core purpose and packs in essential semantics like fixed-not-affected_through and absence behavior. No sentence is filler, though the structure could be tightened with clearer separation of concerns.

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 explaining the return value, and it does: it lists all major data categories, defines fixed vs affected_through, and clarifies null semantics. An agent has enough context to invoke the tool correctly and interpret the response.

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?

The schema already documents the single 'id' parameter with a format and example ('CVE-2024-3400'), so schema coverage is 100%. The description reinforces that the tool targets one CVE but adds no parameter-level detail beyond the schema.

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 opens with 'Full intelligence record for one CVE' and enumerates specific content: CVSS, EPSS, KEV, fixed versions, detection modalities, and news coverage. This clearly identifies the resource and differentiates it from search-oriented siblings like search_cves or get_scoreboard.

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 'for one CVE' plus the detailed record contents make the intended use case clear: when an agent already has a CVE id and needs the full intelligence profile. It does not explicitly name alternatives or state when not to use the tool, but the context is unambiguous.

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