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

The readOnlyHint=true and openWorldHint=false annotations already cover the safety profile. The description adds useful behavioral context by naming the exploitation sources (CISA KEV or explicit reporting), the recency window, and the urgency ordering, but it does not describe pagination or result format.

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 definition is a single, front-loaded sentence with no redundant or filler text. Every phrase contributes to scope, source, recency, or ordering.

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 read-only retrieval tool, the description covers the core domain well and annotations cover safety. However, with no output schema and 0% parameter description coverage, it leaves gaps around the 'limit' parameter and the shape of the returned results.

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 description must compensate for two undocumented parameters. It clarifies that 'days' controls the publication recency window, but it never explains the 'limit' parameter or what the defaults and maximums mean.

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 states a specific resource and scope: vulnerabilities with documented exploitation, within the last N days, ordered by urgency. It is clear what the tool returns, but it does not explicitly distinguish itself from the sibling search_vulnerabilities tool.

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 scope implies when to use it, namely for recent, documented-exploited vulnerabilities, but there are no explicit when-to-use or when-not-to-use instructions. It also does not name alternatives such as search_vulnerabilities for broader queries.

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