get_top_kevs

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 discloses that results are KEV entries and how they are ordered, but says nothing about permissions, rate limits, or freshness/staleness of the catalog. An output schema exists, which reduces the need to explain return values, keeping this at a middling score.

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?

Front-loaded with the core action and source in the first sentence, followed by return ordering and a compact Args block. Every sentence carries information an agent needs; no filler.

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 two-parameter read tool with an output schema, the description covers purpose, return ordering, and both parameters adequately. The remaining gap is routing guidance against the four sibling tools, which the description never addresses.

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% and the schema lacks ranges or enums, yet the description supplies the missing semantics: limit is 1-50 with a default of 10, and sort_by takes 'date_added' or 'epss_score' with their meanings spelled out. This fully compensates for the empty schema descriptions.

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?

States a specific verb and resource ('Fetch actively exploited vulnerabilities from the CISA KEV catalog') and pins the exact data source, which is more specific than generic vulnerability search. It does not, however, explicitly contrast itself with siblings like search_vulnerabilities or get_epss_score, so the differentiation is left to inference.

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 ('actively exploited vulnerabilities' from CISA KEV) implies when the tool is appropriate, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this is the KEV-listing tool rather than the general search tool.

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