check_kev_epss_exposure

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

With no annotations, the description clearly discloses important behavior: it uses external non-Tenable sources, assigns an ordered signal classification, sorts results by urgency, and warns that each plugin incurs an extra Tenable API call. It does not cover error handling or rate limits, but the cost implication and signal ordering are valuable.

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 organized with a clear lead, bullet list, and workflow notes; every sentence adds context about data sources, ranking, cost, or filtering. It is slightly longer than strictly necessary but remains focused and front-loaded.

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 description covers the tool's main purpose, output signal order, cost implications, and suggested preceding filters, while an output schema exists to document return values. The missing explanation of the EPSS threshold parameter and lack of annotations keep it from being fully 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 schema has 0% description coverage, and the text explains `limit` (bounds plugin CVE lookups and API calls), `severity`, and `plugin_family` (filtering similar to search_vulnerabilities). However, `epss_high_confidence_threshold` is never described, leaving its meaning and default (0.5) unexplained despite being central to the EPSS signal classification.

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 'cross-reference[s] live findings against two independent, publicly sourced exploitation signals' (CISA KEV and FIRST.org EPSS) and explicitly distinguishes itself from Tenable's VPR and the sibling compare_vpr_reprioritization tool. This provides a specific verb+resource and differentiates it from related tools.

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?

It gives clear context: use alongside compare_vpr_reprioritization for vendor-independent re-prioritization evidence, and filter by severity/plugin_family first. It references search_vulnerabilities for consistent filtering, but does not explicitly state when not to use the tool or name alternative tools for substitutions, so it lacks full exclusion guidance.

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