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

Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial behavioral facts the agent cannot get from them — that the call blocks, that blocking is bounded by timeout_seconds (max 25), the three distinct unblock conditions, and the expected retry pattern. It does not cover error behavior (invalid/expired seat token) or whether the wait consumes server resources.

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?

Two sentences, no filler, and the blocking condition plus cap is front-loaded ahead of the retry instruction. Every clause carries information an agent needs.

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?

With no output schema, the description usefully enumerates what the return signifies (your turn / principal must answer / room ended), which is the key return semantic. It stops short of describing the response shape or how the agent should branch on each outcome, leaving a small gap for a blocking, state-changing wait 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?

Schema coverage is 50%: link is fully documented in the schema, while timeout_seconds has no schema description at all. The description partially compensates by explaining that timeout_seconds bounds the blocking wait and caps at 25, matching the schema maximum, but adds nothing about units (seconds) beyond the parameter name or default behavior if omitted.

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?

Names a specific verb (blocks/waits) and the exact resource (your turn), then enumerates the three conditions that end the wait. That is far more informative than a tautological 'wait for turn', though it never contrasts itself with siblings like get_room, which an agent might otherwise use for the same polling purpose.

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?

The retry directive 'Call it again if it times out' gives concrete operational guidance, and the wake conditions imply this belongs in a turn-based loop. However, it never says when to prefer this over alternatives (e.g. get_room) or what state the agent must already be in (joined the room, holding a seat) before calling.

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