triage_cve

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

Discloses that each CVE triggers an individual NVD API call with timing estimate. Annotations confirm read-only, idempotent, open-world. No contradictions.

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: first states purpose, second provides critical behavioral detail. No redundant information. 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?

Given output schema exists, description is sufficient: covers purpose, data sources, and performance implication. No missing context for a triage tool.

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?

Single parameter 'cve_ids' is fully described in schema with example and max length. Description adds no additional semantics beyond schema coverage.

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?

Description clearly states the tool triages CVEs using EPSS, CVSS, and KEV. It differentiates from siblings like search_cve and get_cve_detail by specifying the combined data sources.

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?

Provides explicit performance note about NVD API calls and timing, implying optimal use cases. Lacks direct comparison to alternatives but gives strong context for deciding when to use.

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