cve_lookup

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

With no annotations, the description carries the full burden of transparency. It discloses the data sources (NVD and CVE.org) and enumerates the returned fields (CVSS scores, CWE mappings, affected products, references, exploit cross-references). It does not cover potential rate limits or error behavior, but for a read-only CVE lookup this is reasonable. No contradictions with annotations exist (none provided).

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 well-organized with a summary, Returns list, and Args/Returns sections. It is front-loaded with the primary purpose. However, there is slight redundancy: the first paragraph lists return items that are partially repeated in the Returns section. Still, every sentence earns its place and the length is appropriate.

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 simple one-parameter tool with an output schema, the description is complete. It explains the input format, the data sources, and the expected return content. There is no ambiguity about what the tool does or how to invoke it. The existing output schema covers return structure, so the description doesn't need to over-explain.

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 provides only a type 'string' for cve_id with 0% description coverage. The description compensates thoroughly by explaining the required format 'CVE-YYYY-NNNNN' and providing a concrete example ('CVE-2024-1234'). This adds essential meaning beyond the bare 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 clearly states the tool 'Fetch complete details for a specific CVE' from NVD and CVE.org, using a specific verb ('Fetch') and resource ('specific CVE'). This distinctly differentiates it from the sibling tool 'cve_search', which implies searching rather than fetching a known, single CVE.

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 explicitly says 'for a specific CVE', indicating the tool is intended for when a known CVE ID is available. It does not explicitly name alternatives or exclusions, but the word 'specific' provides clear context against the sibling search tool. The guidance is clear enough for an agent to decide when to invoke it.

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