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

With no annotations provided, the description carries the full behavioral burden. It discloses the cost ($0.001 per call), the payment rail (x402 on USDC/Base), and extra response elements (provenance chain and Ed25519 attestation). This goes beyond typical descriptions, though it omits error behavior and rate limits. The transparency is strong but not exhaustive.

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, information-dense sentence. It front-loads the core purpose, then appends pricing and response extras. Every clause adds value, with no filler or redundancy.

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 two-parameter lookup with no output schema and no annotations, this description is nearly complete. It covers the purpose, cost, payment flow, and notable response characteristics. It does not describe error handling or rate limits, but these are minor for a simple CVE lookup, and the description is sufficient for an agent to decide whether and how to invoke the tool.

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 50% (payment is already described in the schema, while id has no description). The description adds critical meaning by clarifying that 'id' is the CVE identifier, which is the main parameter. However, it does not specify the exact CVE format (e.g., CVE-YYYY-NNNNN) beyond maxLength, and payment details are repeated from the schema. It compensates well for the gap but not completely.

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 ('detail'), the resource (NVD CVE), and the lookup key (CVE identifier), while enumerating the returned data (description, CVSS metrics, CWE mapping, dates). This clearly distinguishes it from siblings such as kev_status_by_cve or cve_published_daily_summary, which serve different purposes.

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 implies when to use the tool – when a user needs a single CVE's detailed data by identifier – but it does not explicitly contrast it with alternatives like kev_status_by_cve (for KEV status only) or cve_published_daily_summary (for a daily digest). The usage is clear enough not to mislead, but the guidance is only implied, not stated.

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