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

Although annotations already state read-only, idempotent, and non-destructive behavior, the description adds meaningful context: no side effects, verified NIST NVD source, 1-hour cache, and the specific fields returned. This goes beyond the structured annotations and helps an agent anticipate freshness and provenance.

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, then covers usage rules, source, cache, and fallback behavior in a compact logical flow. Every sentence adds operational value, and the structure helps an agent scan it quickly.

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?

For a single-parameter lookup tool with annotations and an output schema, the description is fully sufficient. It explains the return payload, provenance, caching, when to choose an alternative, and what to do if the result is inadequate. No critical context is missing.

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 documents cve_id with format and required status at 100% coverage. The description repeats the format and requirement but does not add substantial new meaning beyond what the schema provides. Baseline 3 applies.

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 states a precise verb and resource: 'Fetch full detail for a specific CVE by ID.' It also distinguishes itself from security_fetch_package_vulnerabilities by naming the sibling and clarifying the different query intent. An agent can clearly identify what this tool does and what it does not do.

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 gives explicit when-to-use guidance: use when you have a CVE ID and need complete detail beyond package-scan results, and use the sibling instead when you need all CVEs for a package version. It even provides a fallback action via report_feedback if the response does not satisfy the user's need.

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