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

No annotations are provided, so the description carries the full burden. It implies a read-only query against the KEV catalog but does not state whether it returns a boolean, status, or details, nor any limitations (e.g., missing CVE handling). The behavioral disclosure is minimal but not contradictory; it adds a hint of what the tool does without misrepresenting it.

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 a single, succinct sentence with no redundant wording. It front-loads the core function, but its brevity comes at the cost of omitting essential usage details. It is well-structured for its length, though not comprehensive.

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?

Despite having an output schema (which covers return values), the tool's single input parameter is completely unexplained, and there is no guidance on usage or behavior. The description is inadequate for an agent to correctly invoke the tool, especially given the large sibling list that could cause confusion.

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?

The input schema has one parameter 'q' with 0% description coverage, and the tool description does not mention the parameter at all. It does not clarify that 'q' should be a CVE ID or any expected format. The description fails to compensate for the schema gap, leaving the agent without guidance on what to pass.

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 the tool checks if a CVE is actively exploited per the CISA KEV catalog. It uses a specific verb ('is') and resource, and the mention of 'KEV catalog' distinguishes it from siblings like cve_severity or cve_poc_checker. However, it could be more explicit about the input being a CVE ID, so it's not perfect.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or contrasting sibling tools. An agent must infer its use case from the purpose alone, which is not sufficient for proper tool selection.

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