CVE MCP Server

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

With no annotations provided, the description carries the full burden and adds valuable behavioral context: it discloses lazy downloading with a 24-hour cache and that it searches technique descriptions and references. This goes beyond the input schema, though it doesn't cover aspects like rate limits or error handling.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by behavioral details and parameter explanation. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 moderate complexity (1 parameter, no annotations, but with an output schema), the description is mostly complete. It covers purpose, behavior, and parameter semantics adequately. Since an output schema exists, it doesn't need to explain return values, but could benefit from more explicit usage guidelines.

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 description adds significant meaning beyond the input schema, which has 0% coverage. It explains the 'cve_id' parameter with an example (CVE-2021-44228) and clarifies its purpose as a CVE identifier, compensating well for the schema's lack of descriptions.

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 with specific verbs ('Map', 'Downloads', 'Searches') and resources ('CVE', 'MITRE ATT&CK techniques', 'threat groups'), distinguishing it from siblings like 'lookup_cve' or 'get_cve_summary' by focusing on ATT&CK mapping rather than general CVE information.

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 context by specifying it maps CVEs to ATT&CK techniques, suggesting it's for threat analysis. However, it lacks explicit guidance on when to use this tool versus alternatives like 'compare_cves' or 'get_cve_timeline', which could help agents choose more precisely.

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