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

Beyond the annotations (readOnlyHint=true), the description adds substantial behavioral context: the verdict is at the response root applying to the batch, the global hint pointing to cve_lookup, rate limits (30/hr free, 500/hr Pro), and the slim vs. full payload behavior. This goes well beyond what annotations provide.

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 description is dense and information-rich, front-loaded with the core purpose. Every sentence earns its place (usage, payload behavior, response structure, rate limits), though it is slightly long. It could be tightened but remains efficient for the complexity it covers.

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?

Given the tool's complexity (pagination, include modes, response shape, verdict placement, hint), the description covers all essential aspects: purpose, alternatives, payload details, rate limits, and return object. The output schema also exists, so the description appropriately complements rather than duplicates return value documentation.

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%, but the description adds value by explaining the trade-off of the include parameter ('slim default avoids description/summary duplication that bloats 50-item leading lists') and clarifying that 'full' gives the 'same payload shape as cve_lookup'. This contextualizes parameter choices beyond the schema's raw definitions.

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?

The description uses a specific verb ('List') and identifies the exact resource ('CVEs indexed from MITRE/GHSA BEFORE NVD publication'), which clearly distinguishes it from sibling tools like cve_search (published NVD data) and cve_lookup (drill-down). This is a model of purpose clarity.

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?

Explicit guidance is given: 'Use for threat intelligence on emerging CVEs; use cve_search for published NVD data' and 'for drill-down on a single CVE prefer cve_lookup'. This directly addresses when to use this tool versus alternatives, exceeding basic usage context.

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