cve_compare

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

No annotations are provided, so the description carries the full burden. It lists the output fields (CVSS, EPSS, KEV, etc.) but does not disclose behavioral traits like whether it fetches live data, any prerequisites (both CVEs must exist), or error handling. The description is adequate but lacks depth in behavioral transparency.

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 concise, consisting of two sentences that front-load the action ('Compare two CVEs') and then enumerate the output elements. No redundant or unnecessary information. Every sentence earns its place.

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 adequately covers what the tool returns (CVSS, EPSS, KEV, affected products, risk scores, comparison summary). However, it could be more complete by mentioning prerequisites (e.g., both CVEs must exist) or error handling. Still, it provides sufficient context for a comparison tool among many siblings.

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?

The input schema already provides clear descriptions for both parameters ('First CVE ID' and 'Second CVE ID') with 100% coverage. The tool description does not add further parameter-specific meaning beyond repeating the purpose. Baseline of 3 is appropriate.

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 clearly states the tool's purpose: 'Compare two CVEs side by side.' It lists specific elements shown (CVSS, EPSS, KEV status, affected products, risk scores) and mentions a comparison summary. This distinguishes it from sibling tools that focus on single CVEs or lists.

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?

The description implies usage when you need to compare two CVEs, but it does not explicitly state when not to use it or suggest alternatives. For example, it does not mention that for a single CVE, one should use enrichment tools like cve_enrich. The usage context is implied rather than explicit.

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