get_vulnerability

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds significant context: return of CVSS, EPSS, exploit ranking order (Metasploit > ExploitDB > GitHub), and flagged trojans. No contradictions with 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?

The description is a single dense paragraph that effectively conveys all necessary information without redundancy. Could be slightly more structured (e.g., bullet points) but every sentence is informative.

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?

Despite no output schema, the description thoroughly explains the returned data: CVSS, EPSS, CISA KEV, affected products, exploit ranking, Nuclei templates, references. It covers the essential aspects for a single-item lookup tool.

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 covers the single parameter cve_id with pattern and description (100% coverage). The description adds examples and clarifies acceptance of both CVE and EIP IDs, providing slight additional meaning beyond the schema.

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 it retrieves a full intelligence brief for a specific vulnerability, specifies accepted identifiers (CVE/EIP), and lists extensive return fields. This distinguishes it from siblings like search_vulnerabilities and get_exploit_analysis.

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 have a specific vulnerability ID and need comprehensive details, but it does not explicitly state when not to use it or provide direct comparisons to sibling tools. Clear context but no exclusions.

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