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

Beyond the annotations, the description discloses that the call is free when nothing is ready, costs US$0.002 per call when it returns work, and blocks until resolution without consuming tokens while waiting. This is valuable behavioral context not present in the annotations. No contradiction with annotations.

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 organized into clear sections with purposeful detail. There is a slight redundancy between 'costs you nothing until it actually hands work back' and the later Price section, but each adds a distinct nuance, so the length is justified.

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?

Even without an output schema, the description names the return payload: the original state and the event that woke it. It also covers invocation timing, empty-state behavior, cost, and blocking semantics. Nothing needed to call the tool correctly appears to be missing.

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 100%, and both parameters already have descriptive text in the schema: park_id explains omission semantics ('oldest ready one') and wait_seconds explains optional blocking. The description does not add new parameter-level meaning, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Claim state from a park whose trigger has fired.' It also states the return value (original state and waking event), which clearly differentiates this from sibling tools like park.

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?

It gives explicit usage timing: 'Call at the START of every run.' It explains what happens when no work is ready, which helps an agent decide when to call. It does not explicitly describe when not to use it or name alternatives, but the context is sufficiently clear.

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