CVE Intelligence

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

The annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) establish a safe read operation. The description adds the composite/structure context (three components: CVE detail, exploitation velocity, detections), which is useful behavioral framing. However, it doesn't disclose what the exploitation-velocity context entails, how many detections it returns, or the performance cost of this heavier composite call relative to get_cve.

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?

A single concise sentence that efficiently conveys the composite nature of the tool. It front-loads the purpose and uses a colon to enumerate the three components. Slightly dense with jargon ('exploitation-velocity context') but no wasted 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?

An output schema exists, so return-value documentation is covered there. The tool is a composite with moderate complexity (three data components). The description names the components but doesn't hint at the cardinality or relationship between them (deciding when one component would be absent, e.g., no detections referencing the CVE). Given the output schema exists and the single parameter is simple, this is adequate but could be richer about edge cases.

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 cve_id parameter, so the schema already documents it fully ('CVE identifier (e.g. CVE-2024-3400)'). The description doesn't add format validation details (e.g., accepted naming conventions) beyond the schema. Baseline 3 is appropriate since schema does the heavy lifting with one simple parameter.

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 states a specific verb+resource ('Composite CVE dossier') combining enriched CVE detail with exploitation-velocity context and detections. It clearly distinguishes from siblings like get_cve (basic CVE) and get_threat_enrichment by noting it's a composite including detections and velocity context.

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?

No when-to-use or when-not-to-use guidance is provided. With nearly 70 sibling tools including get_cve, get_cve_intelligence, and bulk_get_cves, the description doesn't explain when to pick this composite over the simpler get_cve or search_vulnerabilities. The value proposition is implied ('in one call') but no explicit alternatives or exclusions are named.

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