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

Beyond the annotations, the description discloses what data the record returns, notes rejection status and source freshness, and clarifies the scope limit that this is not a system-affected determination. It also adds an important trust-boundary warning that source text is untrusted data and never instructions.

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 three compact sentences, front-loads the core lookup purpose, then adds scope and safety context. Every sentence contributes useful information without repetition.

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 read-only exact-CVE lookup, the description covers the returned record contents, the scope limitation, and the untrusted-source warning. With an output schema present, it need not explain return structure in more detail; the definition is complete enough to invoke the tool correctly.

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 coverage is 100%, and the schema already documents the exact CVE identifier with a pattern and example. The description reinforces that the ID must be exact but does not add syntax or formatting details 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 states a specific verb and resource ('Look up an exact CVE ID') and enumerates what the record contains, including affected products, CVSS severity, references, rejection status, and source freshness. It also distinguishes the result from a system-specific assessment, which separates it from the sibling check_dependencies tool.

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 exact-ID framing tells the agent this is for direct lookups rather than listing updates, and the caveat that this is not a determination of system impact steers away from using it for dependency checking. It does not explicitly name list_cve_updates or check_dependencies as alternatives, so the routing guidance is clear but not fully explicit.

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