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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context beyond that: exploitation provenance (CISA KEV or explicit reporting), result ordering (most urgent first), and pagination via offset/hasMore. It stops short of describing the exact record shape or rate limits, which is acceptable given the read-only annotation.

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 dense sentences with zero waste. The core definition and scope are front-loaded, followed by the disambiguation and pagination note.

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 and minimal parameter documentation, the description provides enough to call the tool correctly: what is returned, the sort order, the pagination contract, and when to use an alternative. The only minor gap is not explaining the limit parameter, but the schema exposes its bounds and default.

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%, so the schema gives only numeric constraints and defaults, not meaning. The description clarifies 'days' as a lookback window and mentions 'offset' for paging, but does not explain the limit parameter or its constraints, leaving part of the parameter semantics to be inferred.

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 resource (vulnerabilities with documented exploitation from CISA KEV or explicit reporting) and scope (published within the last N days, most urgent first). This clearly distinguishes it from the broader search_vulnerabilities sibling.

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?

Explicitly names the use case (briefings like 'what was exploited this week') and the alternative for narrowing by product or keyword (search_vulnerabilities with known_exploited_only). The routing condition is unambiguous.

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