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

No annotations are present, so the description must carry the full burden. It states the content (actively exploited CVEs with deadlines) but does not disclose filtering defaults, pagination, or any side effects. It is arguably a read-only operation, but that is not explicitly stated.

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 consists of two terse, informative sentences with no redundant wording. It front-loads the key concept (CISA KEV) and adds compliance context efficiently.

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 list tool, the description covers the subject matter and compliance context, while the schema handles parameter details. Without an output schema, the description does not specify return fields, but this is acceptable given the straightforward nature of the tool.

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?

All four parameters are fully described in the schema with defaults and examples, so the description does not need to add much. The mention of patch deadlines complements the 'overdue' parameter but adds no new syntax or format details beyond the schema.

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 identifies the tool as providing CISA Known Exploited Vulnerabilities with patch deadlines, and ties it to DORA Art. 9 compliance. However, it does not explicitly distinguish from sibling tools like kev_check or cve_search, so it is not a full 5.

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 mention of DORA Art. 9 patch compliance suggests a compliance use case, but there is no explicit statement of when to use this tool over alternatives like cve_search or kev_check. No exclusions or alternative directives are provided.

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