check_cisa_kev

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 accurately conveys a read-only membership check, but it does not disclose the return shape (e.g., boolean vs. matched record), behavior for CVEs not in the catalog, or data-source freshness. This is adequate for a simple check but not rich.

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?

One front-loaded sentence with no filler. The acronym is expanded and the exact function is stated without redundancy.

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 one-parameter membership check with no output schema, the description is nearly complete: it states the action and input format. It falls short of 5 only because it does not specify the return value contract or mention alternatives when users need broader CVE metadata.

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 100%; the cve_id parameter already has a description and example in the schema. The tool description adds no separate parameter semantics, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Check if a CVE is in CISA Known Exploited Vulnerabilities catalog.' This clearly distinguishes it from sibling CVE/advisory lookups such as nvd_cve_lookup and cisa_search_advisories, despite not naming them.

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 intended use case (verify KEV membership for a CVE) is clear, but the description provides no guidance on when not to use it or which sibling to prefer for other CVE/advisory lookups. Given several similar-looking CISA/NVD tools in the sibling list, explicit routing would strengthen it.

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