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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description adds the non-obvious result ordering ('newest first') and the full field projection including EPSS and ransomware flags. It stops short of describing pagination or what a truncated 10-item default means for completeness.

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?

Two sentences: the first packs catalog identity, ordering and output fields; the second packs usage modes and the sibling hand-off. Front-loaded with the resource, zero filler.

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?

With no output schema, the description usefully enumerates what comes back (CVE, vendor, product, dates, ransomware flag, required action, EPSS, AI-stack flag). Combined with the stated lookup modes and the get_cve alternative, an agent has everything needed to call it 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 description coverage is 83%, so the schema already documents cve, query, since, ai_stack and ransomware. The description maps lookup modes onto those parameters but says nothing about 'limit' or 'ransomware', and adds no format or combination detail beyond the schema text. Baseline 3 for high coverage.

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 ('search') and resource (CISA's KEV catalog) plus the exact return fields, and explicitly separates the tool from get_cve. An agent can identify both the tool's domain and its scope without opening the schema.

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?

Enumerates the four concrete invocation modes (single CVE, vendor/product words, since-a-date, AI-only) and names the alternative tool with its selecting condition: 'For one CVE in full, use get_cve.' No inference required.

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