security_fetch_cve_detail

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

Discloses return fields (severity, CVSS score, affected versions, fix information) beyond the schema. No annotations exist, so description carries full burden. Does not mention read-only nature or authentication, but the fetch semantic is implied.

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?

Three short sentences, each adding unique information: purpose, usage example, and expected output. No redundant or filler content.

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 simple single-parameter tool and existence of an output schema (though not shown), the description covers what the tool does, how to call it, and what to expect. No additional context needed.

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?

With 0% schema description coverage, the description provides crucial meaning: the full CVE ID format with a concrete example (CVE-2021-44228). This compensates fully for the schema's lack of description.

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 verb 'get' and the resource 'full detail on a specific CVE', distinguishing it from sibling tools like security_fetch_package_vulnerabilities which return package-level vulnerability 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?

Provides explicit instruction to supply a CVE ID with an example (CVE-2021-44228), guiding proper invocation. Does not mention when not to use or alternatives, but the sibling tools naturally diverge in purpose.

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