Sync recent CVEs

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

Annotations indicate idempotentHint=true and openWorldHint=true, and description adds that it contacts a fixed NVD endpoint and does caching behavior. This matches well—the description confirms it's safe to call repeatedly. It also implies it writes to cache (destructiveHint=false is consistent). No contradiction.

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 two concise sentences with no filler. The first sentence states the core action and limits, the second clarifies it's a safe network call. Every word adds value.

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 the output schema exists (so return format is documented elsewhere) and annotations cover idempotency and non-destructive behavior, the description sufficiently explains the tool's role among many sibling vuln tools. The key constraints (120-day window, official endpoint, caching) are clearly stated.

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 50% (only start and end have descriptions; mode and limit lack descriptions in schema). The description adds that the window is of at most 120 days, which partially compensates, but doesn't explain mode enumeration or limit semantics beyond what's in schema. Baseline 3 is appropriate since the description provides some additional constraint context.

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 fetches and caches NVD CVEs from a UTC window, uses a specific verb (sync), and distinguishes from siblings by specifying it contacts the official NVD endpoint and does not scan a target. This differentiates it from vuln_search_cves, vuln_get_cve, and other vuln 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?

The description explicitly says the window is for one published or modified UTC range of at most 120 days, and states it contacts the fixed NVD endpoint (not scanning). While it doesn't explicitly specify when not to use (e.g., when to prefer vuln_search_cves), the context and sibling names make it clear this is for bulk import vs. search.

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