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

Annotations already cover read-only/non-destructive/non-open-world, and the description adds genuine traits beyond them: non-blocking execution, incremental-since-last-check semantics, and a paid-plan requirement. It doesn't cover edge behavior such as no-new-matches or limit exhaustion, which keeps it from a 5.

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?

Three short sentences, no waste, with the core action and the non-blocking trait front-loaded and paging guidance immediately after. Every sentence earns its place.

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?

An output schema exists, so return values needn't be described, but the description never explains how the monitor is identified (presumably via `token`) and doesn't note that `limit` defaults to 25 and caps the batch. For a paged read tool with a 0%-documented schema, those are noticeable gaps.

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 description coverage is 0%, so the description must compensate, and it does explain since_hit_id's paging role well. However, `token` and `limit` get no explanation at all — notably, it never says `token` is the monitor's identifier, which is the single most important semantic here given there is no monitor_id parameter.

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?

States a specific verb and resource — collect matches for a monitor — and adds the key qualifier "without blocking," which separates it from a blocking poll. It doesn't explicitly contrast with list_monitors or update_monitor, so the sibling differentiation is implied rather than stated.

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?

"Pass since_hit_id to page forward and see only what is new since your last check" gives a concrete incremental-check workflow, and "Requires Keeploop Pro" is a real prerequisite. It stops short of saying when to use this versus list_monitors or what happens on a first check with no prior hit.

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