security_fetch_cve_watch_status

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

With no annotations, description fully discloses behavior: per-user cursor, first call returns 30 days, subsequent only newer, sourced from Redis, no external API calls, instant. No hidden side effects or 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?

Well-structured with purpose first, then efficiency, param detail, behavior notes, and a fallback action. Slightly lengthy but each sentence adds value; no redundancy.

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?

Covers all necessary aspects: purpose, param semantics, usage pattern, behavior, caching mechanism, source, and error handling. Output schema exists but is not required to be described. Ties to sibling 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?

Parameter watch_ids is explained as 'List of watch IDs to check — same IDs used when creating watches' and marked Required. This adds critical context absent from the minimal schema (only items: {}).

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?

Clearly states the verb 'Check' and resource 'CVE watches', distinguishes itself by returning only new events, and implies it's for polling on a schedule. Efficiently differentiates from sibling security_fetch_cve_watch (creation).

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 context for scheduled polling, mentions it returns only new events for efficiency, and ties parameter to creation tool. Does not explicitly list alternatives or when not to use, but sufficiently guides typical use cases.

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