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

Annotations cover safety (readOnly/idempotent/openWorld), and the description adds substantial extra context beyond them: x402 pricing and payment location, the queued-not-charged error behavior, the no-charge-on-invalid-input/failure policy, and an explicit AI-generated disclaimer on the attack flow.

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?

Dense but well front-loaded: capability inventory first, then operational caveats (caching, pricing, error handling). Nearly every clause earns its place, though the enumeration is long enough to verge on a feature dump.

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 responsibly enumerates what comes back, and it covers payment, error, and caching behavior. An agent has everything needed to call it correctly and interpret the result.

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% for the single id parameter, and the description adds no syntax or format detail beyond the schema's pattern and example. Baseline 3 when the schema carries the load.

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?

Opens with a specific verb+resource framing ('Everything an agent needs to prioritize one CVE') and then enumerates the exact payload (CVSS, KEV, EPSS, ATT&CK, D3FEND). It is clearly a per-CVE enrichment tool and is distinguishable from siblings like cve_batch_intel and cve_status.

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?

Explicitly tells the agent to check cve_status (free) first and explains the uncached-CVE case. It does not, however, route the agent to cve_batch_intel for multi-CVE work, which is the obvious alternative for batch use.

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