AIS CVE Priorities — daily exploit-ranked patch list for AI agents

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

No annotations are provided, so the description must convey behavior. It indicates a read-only, non-destructive operation (a 'teaser' that returns information), and does not imply any side effects. While it does not explicitly state 'read-only', the nature of the tool and its purpose make it clear.

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 extremely concise (two sentences) and directly states the purpose, ranking criteria, and alternative tool. No redundant information or fluff.

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 lacking an output schema, the description sufficiently indicates the return content (top-3 CVEs, no scores) and points to a sibling tool for details. It is complete for the tool's limited scope, though a more explicit mention of the return format would raise it to 5.

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 tool has zero parameters, and the schema is fully covered (empty properties). There is nothing for the description to add; no ambiguity exists regarding input semantics.

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: it returns today's top-3 CVE priorities based on a specific ranking (KEV + EPSS + KEV-recency) and explicitly distinguishes itself from the sibling tool 'top_cves_today' which provides the full scored list.

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 explicitly tells when not to use this tool ('Use top_cves_today for the full scored list') and explains the ranking rationale, guiding the agent to select the appropriate tool based on whether scores are needed.

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

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

With no annotations, the description carries the full burden, and it does disclose a critical behavioral trait: the tool is paid, with concrete pricing ($19/30 days, campus pass, $0.005 per x402 call). However, it says nothing about what a 'priority verdict' contains, rate limits, or return format, so the operational picture is only half-complete.

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?

Two sentences, with the important PAID flag front-loaded and the pricing detail compactly packed. The first sentence is dense but every element (key, campus pass, x402, price) is operationally necessary; only mild bloat from listing three payment paths.

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 single-parameter tool with no output schema and no annotations, the description covers the payment gate but leaves the actual return value — what a 'priority verdict' is — unexplained. An agent knows it must pay but not what it receives, so it is minimally adequate rather than 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?

Schema coverage is 100% — cve_id is documented as 'CVE-YYYY-NNNN' — so the schema already carries parameter meaning. The description adds nothing about the identifier format or constraints, making the baseline 3 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 final sentence states a specific resource and scope: 'One CVE's priority verdict from today's AIS ranked set,' naming the input implicitly. It does not explicitly differentiate from siblings like top_cves_today or kev_fresh, so the agent must infer that this is the single-CVE lookup versus a list.

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?

There is no guidance on when to use this tool versus brief_teaser, kev_fresh, or top_cves_today. The description covers payment mechanics but not selection criteria, leaving the agent to infer the use case.

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

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

With no annotations provided, the description carries the behavioral burden and does disclose the key trait an agent needs: this is a paid/gated resource requiring an AIS CVE key, campus pass, or x402 per-call payment, with explicit prices. It stops short of describing rate limits, quota exhaustion behavior, or what happens without a key.

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?

Two sentences, both dense and free of filler, but the structure is inverted: pricing and URLs consume the entire first sentence while the actual purpose trails in the second. An agent scanning the opening clause sees commerce before function.

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 zero-param tool with no output schema, the description should sketch the return shape; 'complete catalog with today's AIS ranks' is suggestive but leaves the record fields, ordering, and count unspecified. The access/payment model is well covered, so the gap is confined to return-value expectations.

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 tool takes zero parameters, so the baseline of 4 applies; there is no parameter syntax for the description to clarify or for the (empty) schema to omit.

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 second sentence names a specific resource and scope: CVEs added to CISA KEV in the last 7 days, complete catalog, with today's AIS ranks. This distinguishes it from the 'today'-scoped sibling top_cves_today, though the differentiating 'last 7 days' framing is buried behind the paywall preamble rather than front-loaded.

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 explains how to gain access and pay, but nothing about when to choose this tool over brief_teaser, cve_verdict, or top_cves_today. No exclusions, no stated conditions of use beyond the paywall.

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

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses the access model (paid key, campus pass, or x402 per-call pricing) which an agent must know. However it omits return format, rate limits, or pagination, so disclosure is partial.

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 monetization sentence leads the description and pushes the actual purpose to the end. Every sentence earns its place, but the front-loading prioritizes pricing over what the tool does, which is weaker structure for tool selection.

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?

With no output schema, the description helpfully enumerates the returned fields (scores, KEV, EPSS, patch status, methodology). For a zero-param, zero-annotation tool, this is close to sufficient, lacking only return-format detail.

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 tool takes zero parameters, so there is nothing for the schema to document and the description needn't compensate. Baseline of 4 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?

States a specific verb+resource: 'Today's FULL ranked CVE priority list with scores, KEV, EPSS, patch status, and methodology.' An agent knows exactly what it returns. It doesn't explicitly differentiate from siblings like brief_teaser or cve_verdict, though 'FULL' implies it is the complete version.

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?

No guidance on when to choose this over the sibling tools. The word 'FULL' hints it is the exhaustive counterpart to a teaser, but no alternative is named and no context for selection is provided.

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