nist-mcp

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

Annotations indicate read-only and open-world hints, but the description adds valuable behavioral context: it discloses potential performance ('May take 6+ seconds') and rate-limiting constraints ('due to rate limiting'), which are not covered by annotations. This enhances transparency beyond the structured data.

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 front-loaded with the core purpose, followed by usage guidance and behavioral notes. Each sentence serves a distinct purpose (detail listing, usage context, performance warning), with no wasted words, making it highly efficient and well-structured.

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 (detailed CVE data), the description is complete: it outlines what information is returned, usage context, and behavioral constraints. With annotations covering safety and an output schema likely detailing return values, no significant gaps remain for agent understanding.

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 has 100% description coverage, clearly documenting the 'cve_id' parameter. The description does not add further semantic details about the parameter beyond what the schema provides, so it meets the baseline for high schema coverage without extra value.

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 explicitly states the action ('Get full details for a CVE') and lists specific resources returned (description, CVSS scores, affected products, etc.), making the purpose clear and specific. It distinguishes from sibling tools like 'search_cves' by indicating this is for detailed information after searching.

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 provides explicit guidance on when to use this tool ('Use this after search_cves to get complete vulnerability details'), clearly differentiating it from the sibling 'search_cves' tool. It also mentions an alternative context (rate limiting without an API key), though not a direct alternative tool.

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