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

With no annotations provided, the description carries the full burden. It discloses the data sources (NIST NVD and GitHub Security Advisories), the filtering capabilities, and even the cost structure ('Keyless. [$0.01/call]'), giving a transparent picture of the tool's behavior without hidden side effects.

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 informative and packed with details, yet it remains structured and readable. It could be slightly more compact by trimming the redundant example, but overall it is efficient and well-organized.

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 tool's moderate complexity, the description covers all essential aspects: purpose, data sources, output fields, parameters, example usage, and cost. It even notes the absence of authentication ('Keyless'), making it sufficiently complete for an agent to decide when and how to use it.

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?

Although the schema only exposes a generic 'params' object, the description details the meaningful keys (cve_id, keyword, severity, source, maxItems) with formats and examples. This adds substantial semantic meaning that the schema alone lacks, effectively documenting the parameters despite the generic structure.

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 a specific action ('CVE vulnerability lookup') and the subject ('security vulnerability records'), making it distinct from sibling tools like serp or domain_info. It enumerates the data fields returned, so an agent immediately knows what this tool does.

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?

It explicitly suggests when to use the tool ('For vulnerability triage and dependency risk checks'), providing clear context. However, it does not explicitly contrast with alternatives or state when *not* to use it, so it falls slightly short of full explicit guidance.

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