fetch

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the description does not need to repeat safety traits. It adds useful context by specifying the returned content: official data, AI explanation, research, and source URLs. It does not cover not-found behavior or rate limits, but the remaining gap is minor for this simple lookup.

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 definition is a single, front-loaded sentence with no filler. Every phrase earns its place by stating the action, the input constraint, and the returned 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?

For a one-parameter lookup tool with no output schema, the description is nearly complete: it explains what is fetched, how it is identified, and what data comes back. The only meaningful omission is what happens when the exact ID is not found.

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 0% for the single id parameter, so the description must carry the semantic burden. It does so partly by saying the ID must be exact, which implies an exact-match identifier rather than a fuzzy search term. It does not specify the expected CVE ID format or provide an example.

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 and resource: fetch one CVE by exact ID, and it lists the data returned. It implicitly distinguishes exact-ID lookup from search-style siblings, but it does not differentiate itself from the sibling get_cve, which appears to serve a similar purpose.

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 phrase 'by its exact ID' implies this tool is for direct lookup when the exact CVE identifier is known, while search tools handle discovery. However, it does not explicitly name search or search_cves as alternatives, nor does it state when not to use this tool.

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