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

With no annotations, the description carries the full burden and does well: it discloses the payment gate ($0.01 x402, PAYMENT-SIGNATURE header, or Gumroad X-API-KEY), the 50-result cap, the cost of the call, and the near-match caveat from keyword search. It omits rate limits, error/insufficient-payment behavior, and whether the version parameter is exact or fuzzy, so not quite a 5.

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?

Front-loaded with the core purpose, then cleanly labeled sections for differentiation, exclusions, and behavior. Every section earns its place, though the branding prefix and all-caps labels add minor noise.

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?

No output schema exists, and the description compensates by naming the returned fields (CVSS, CISA KEV, EPSS where offered), the sort order, and the result cap. Payment, usage boundaries, and caveats are all covered for a 4-param discovery 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 description coverage is 100%, so all four parameters are already documented with examples. The description adds only that version is optional and that KEV status is part of the enrichment; it adds no syntax or matching-semantics detail (e.g. whether version is exact) beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource ('returns CVEs affecting a given vendor/product'), names the enrichment (CVSS, KEV, EPSS) and ordering, and explicitly distinguishes itself from get_cve_details and get_cve_batch. An agent can route correctly without opening any schema.

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?

Provides explicit when-to-use ('discovering CVEs by vendor/product when you do not already have an exact CVE id'), when-not-to-use, and named alternatives for the exclusion case. The NVD-keyword-vs-CPE caveat further clarifies the appropriate context.

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