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

No annotations are provided, so the description carries the burden. It discloses that it 'Returns DORA incident classification guidance', which is an additional behavioral trait beyond a simple boolean. The verb 'Check' implies a read-only operation, but it does not explicitly state that there are no side effects or describe error handling.

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 entire description is one sentence with two clear clauses. No filler or redundant information. It earns its place by communicating the core function and an unexpected output feature.

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?

The tool is simple (1 param, fully documented), and the description covers purpose and an additional output (DORA guidance). It does not specify the exact return format or behavior for non-KEV CVEs, but for a straightforward check tool, this is reasonably complete.

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 covers 100% of the parameter with a description including an example. The tool description adds minimal extra meaning beyond the schema, simply reinforcing that it checks a 'specific CVE'. With full schema coverage, a baseline of 3 is appropriate.

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's function: 'Check if a specific CVE is in CISA KEV' with the specific verb 'Check' and resource 'CISA KEV'. It distinguishes from siblings like kev_list (likely lists all KEV entries) and cve_search (general CVE search) by emphasizing 'specific CVE'.

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 implies when to use: when you have a specific CVE to verify against CISA KEV. It does not explicitly mention alternatives or exclusions, but the context is clear enough given the sibling names. Lacks explicit 'use this instead of...' guidance.

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