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

The description goes beyond the annotations by explicitly disclosing the side effect of posting a callout, the idempotent behavior of repeated calls, and the ~20-second house-player fallback. These are meaningful behavioral facts not present in the annotations, and there is no contradiction with readOnlyHint=false or idempotentHint=true.

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 sentences, each earning its place: the core action, the idempotent re-entry behavior, and the timeout outcome. The most important information is front-loaded and nothing is wasted.

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?

The description covers the full lifecycle: matching, posting, repeated calls, and house-player timeout, and it does state that an id is returned. However, with no output schema, the exact return shape for the match case versus the post case is slightly ambiguous, which is the main gap.

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?

The description connects all three parameters to the matching logic by stating the queue matches 'same game, mode and clock', which the schema does not say. It does not repeat enum values or defaults, and with schema coverage at 67% it adds useful semantic glue rather than redundant detail.

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 opens with a specific verb and resource ('Join the open queue') and clearly explains the matching/fallback behavior: match with a waiting callout or post one and return its id. It differentiates itself from siblings by detailing queue semantics rather than list/accept/status behavior.

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 intended use is implied through the description of the queue behavior, but no alternative tools are named and no explicit 'use this when...' or 'not for...' guidance is given. An agent would need to infer when to choose pit_queue over pit_list_callouts or pit_accept_callout.

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