websex_cve_lookup

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

No annotations are provided, so the description carries the full burden. 'Without inventing intelligence' gestures at returning authoritative, non-hallucinated data but discloses nothing concrete about auth needs, rate limits, or lookup failures/misses for a network-backed NVD call.

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?

A single front-loaded sentence naming the action and source. The trailing 'without inventing intelligence' clause is colorful but adds little operational value.

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 simple one-parameter read tool with an output schema covering return values, the description is nearly sufficient. Its main gap is the absence of input format guidance and any behavioral caveats.

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 description coverage is 0% for the single required cve_id parameter. The description does not specify the expected format (e.g., CVE-YYYY-NNNN), so it fails to compensate for the schema gap.

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?

States a specific verb (Retrieve) and resource (a CVE record from NVD), so the agent knows exactly what it returns. It does not explicitly differentiate itself from siblings like websex_exploit_search, though the 'from NVD' scoping hints at an authoritative-source lookup.

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?

There is no statement of when to use this tool versus alternatives, nor any preconditions or exclusions. The only guidance is the implied 'CVE lookup' purpose derived from the name.

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