security_fetch_cve_watch

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

The description provides extensive behavioral context beyond annotations: it explains persistence via Redis, daily background refresh from NVD, CISA KEV, EPSS, return structure (has_new_events, events, call_back_in), rate limit (60/min), and no auth. This complements the annotations (destructiveHint, readOnlyHint) without 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 fairly concise for its content, front-loading the core purpose. Each sentence adds value, though it could be slightly trimmed (e.g., the repetition of 'create, check, delete'). The structure is logical: purpose, features, return info, rate limit, target user, fallback.

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 tool's complexity (3 params, all required, multiple actions, persistence), the description covers all necessary context: what it does, how it works (Redis, daily refresh), what it returns, rate limits, auth, and target audience. The presence of an output schema further reduces the need to detail return fields, though the description already mentions them.

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 input schema covers 100% of parameters with clear descriptions. The tool description restates the actions and CVE IDs but does not add new semantic details beyond the schema. Therefore, it meets the baseline for high 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?

The description clearly identifies the tool as a persistent CVE watchlist, specifying the verb 'create, check, delete' and the resource (CVE watchlist). It distinguishes from siblings by emphasizing persistence and periodic updates, and contrasts with one-off CVE queries.

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 targets security engineers tracking CVE exposure over time. It includes a fallback to report_feedback if the tool does not serve the need. However, it does not explicitly mention when to use this tool over siblings like security_fetch_cve_detail or security_fetch_cve_risk_summary.

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