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

Beyond the readOnly/openWorld annotations, it discloses behavior annotations cannot carry: deterministic table lookup with LLM only adding compensating-control prose, a $0.04 USDC x402 price on Base mainnet, the exact failure mode (PaymentRequired challenge), and the retry protocol with a signed payload in _meta['x402/payment']. This is exactly the non-obvious operational detail an agent needs.

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?

Purpose is front-loaded in the first clause, followed by lookup semantics, agent use case, then the pricing/retry mechanics. Five tight sentences with no filler; the payment details are necessary for correct invocation.

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?

With no output schema, the description still names what is returned (triggered compliance controls per framework) and covers the paid-call flow, so an agent can call it correctly. It is silent on whether actor and cve_id may be combined or must be mutually exclusive, which is the one remaining ambiguity.

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 the actor, cve_id, and framework enum are already fully documented in the schema. The description only restates that the query targets 'a CVE or threat actor,' adding no syntax or format meaning, so the 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 and resource ('Returns triggered compliance controls for a CVE or threat actor') and enumerates all 11 frameworks, so an agent knows exactly what is produced. It does not differentiate itself from the closely named sibling getComplianceBatch, which is the main gap keeping it below a 5.

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 triggering context: 'call when a new advisory drops, generate gap report, route to compliance team.' Context is explicit but no when-not conditions or named alternatives (e.g., getComplianceBatch) are offered.

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