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

With no annotations, the description carries the full burden and does so: free-tier quota (10 calls/day/IP), exactly what preview omits vs. what full adds (computed decision, envelope, reasoning, KEV cross-check, signed receipt), the billing default trap, both payment transports (x402 wallet payment, Bearer credits token), and a trial-credit path. This is far more than a restatement of the name.

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 purpose and outcome, then the tier economics, then payment mechanics. Nearly every sentence carries non-schema information (trial URL, strict transport URL), though the pricing/credit figures and tier contents partially duplicate the schema descriptions, adding some redundancy to an already dense block.

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 paid 3-param tool with no output schema and no annotations, the description covers what an agent needs: the required input, the two tiers and their verdict contents, the default/billing edge case, and how to pay. Nothing essential to making a correct call is missing.

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 meaning beyond the schema: the conditional billing behavior of an omitted tier, and the relationship between the payment argument and the alternate Bearer-token / strict x402 transports. It stops short of syntax examples for the payment payload.

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+scope: a signed SSVC patch-urgency decision for one CVE, built on the CISA SSVC Coordinator tree and Vulnrichment decision points. This clearly separates it from siblings like get_cve_record or get_kev_catalog without the agent needing to open a 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?

Gives clear context for when to call it (a single-CVE urgency decision) and exhaustively explains the preview-vs-full choice, including the non-obvious default that omitting tier bills as full when a payment/credits token is attached. It never names a sibling alternative or states when NOT to use this tool, so it falls short of fully explicit routing.

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