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

With no annotations, the description carries the full burden and does it well: it discloses the exact gating logic (BLOCK only on an exploited CVE with no fix, HOLD when a known CVE applies, PASS on no match, UNKNOWN outside the cohort), rate limits (10 calls/day/IP), package caps (3 preview, 10 full), billing triggers, and cost ($0.02/credit). This is far beyond what any structured field provides.

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 content is dense and almost every sentence earns its place for a payment-metered tool, but it is delivered as one long unstructured paragraph. Payment mechanics, tier semantics, and gating logic are interleaved rather than sectioned, hurting scannability and front-loading.

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 describing the return shape: an overall gate plus per-package verdict, with full tier adding matched-CVE evidence (ids, affected ranges, fixed versions, KEV status) and a signed receipt. For a tool of this complexity, an agent has everything needed 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%, so the baseline is 3, but the description adds real value beyond the schema: it names the x402 payment transport, the X-PAYMENT header equivalence, the strict HTTP-402 endpoint URL, the Bearer tf_live_ token form, and the trial-credit claim URL. These are operational details the schema does not carry.

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: it fuses the ingested AI-stack CVE batch with the CISA KEV catalog to produce a BLOCK/HOLD/PASS/UNKNOWN deploy gate. The scope (AI software stack, per-package name@version) is explicit and clearly separable from siblings like get_cve_record or get_kev_catalog, which supply raw data rather than a fused gate verdict.

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?

Explains the conditions that select each tier (omit tier → free preview unless a payment/credits token is present; full costs 1 credit and raises the cap). It gives clear operating context but does not explicitly compare itself against the many sibling verdict tools (ssvc_verdict, check_ai_supply_chain_risk), so an agent gets no stated 'use this instead of X' routing.

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