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

Annotations only declare non-read-only, non-destructive, non-open-world, so the description carries the real load and does disclose the blocking/waiting behavior and the reservation ('claims') semantics that annotations cannot convey. It stops short of saying what happens on timeout or whether a claimed request can be lost, which matters for a long-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?

Three short, front-loaded sentences: what it does, what you owe it, and how to continue. No filler or restated title.

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?

There is no output schema, so the description should say what a call returns when no request arrives within the wait window or what a claimed request looks like. The workflow is complete but the response contract is not.

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%, so all three parameters are already documented. The description references wait_seconds as an upper bound but does not explain the duplicated waitSeconds/wait_seconds aliases or the 25-second cap, so it adds little beyond the schema.

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 gives a specific verb and object: it waits for the next user-requested change in Xodia and claims it, with an explicit wait bound. That separates it in practice from the sibling get_request, though the description never names that sibling or otherwise disambiguates them directly.

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 prescribes the full loop clearly: call this to claim work, do the work, then call reply_to_request, and call again to keep listening. What is missing is any exclusion or comparison, e.g. when to use get_request instead or what to do if nothing arrives.

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