Poll for newly found offers (main wake-up tool)

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

Discloses that it 'clears the queue' (destructive behavior) and that it returns a cumulative set since last call. No annotations are provided, so this description carries the full burden. Could mention rate limits or auth but adequate for a 0-param polling tool.

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?

Highly concise: two sentences that front-load the key behavior and follow with usage guidance. No redundancy or extraneous words.

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 zero parameters and no output schema, the description explains return type, behavior (clearing queue), and scheduling advice. Could mention what happens when no new offers, but overall complete for a simple polling 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?

No parameters exist, and schema coverage is 100%. Baseline of 4 applies as the description adds no parameter information, which is acceptable for zero parameters.

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 it returns new offers (routes/dates or price drops) since last call across all watches. It distinguishes itself as the 'main wake-up tool' and the reliable way to find changes, thus differentiating from siblings like get_watch_offers.

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?

Explicitly advises to call on own schedule (e.g., hourly) rather than relying on push notifications. Implicitly contrasts with notification-based tools. Lacks explicit when-not-to-use but provides clear context for appropriate use.

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