get_recent_cves

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

Without annotations, the description carries the burden of behavioral disclosure. It mentions the NVD API limit of 120 days, which is a key constraint, but does not describe other behaviors like pagination, rate limits, or that it returns a list of CVEs. Output schema exists but is not referenced.

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?

Single sentence, no redundant words, directly communicates the tool's core function and a key constraint. Every part is necessary.

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 tool with two parameters and an existing output schema, the description is mostly complete. It mentions the critical API limit and the time-based nature. However, it lacks guidance on when to use this tool versus siblings, slightly reducing completeness.

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 0%, so description must compensate. It adds meaning for `days_back` by specifying 'last `days_back` days', but does not explain `limit` parameter (default 20) beyond what the schema provides. This partial clarification is insufficient for full compensation.

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 verb 'Fetch' and resource 'recent CVEs', specifies the time window via `days_back` parameter, and differentiates from siblings like search_by_severity or search_cve_by_id by focusing on recency.

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 implicitly conveys when to use (fetching recent CVEs by days back) but does not explicitly state when not to use or compare to sibling tools like search_by_severity or search_cve_by_keyword, leaving room for confusion.

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