CVE Intelligence

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds crucial behavioral info: subscription requirement (Purple tier) and the rich data composition, providing context beyond safety annotations.

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?

Single sentence with dash-separated list of features; efficient, front-loaded, no redundant words.

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 1 required param and an output schema (present but not shown), the description covers the tool's purpose, included data components, and access constraint. No gaps for effective use.

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 100% with parameter description 'CVE ID (e.g. CVE-2025-12345)'. Description does not add new parameter details but contextualizes how the CVE ID is used in the dossier.

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?

Description clearly states 'Composite CVE dossier' and enumerates specific components (CVE detail, linked threats, EPSS, KEV, detection coverage, simulation, timeline), distinguishing it from simpler tools like get_cve_details.

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 states dependency on 'Purple tier ($11.99/mo)', guiding when access is available. Does not explicitly contrast with siblings, but the comprehensive nature implies when to use this over simpler CVE tools.

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