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

Annotations declare a non-readonly, non-idempotent mutation, and the description adds real behavioral detail beyond them: a 60-second visibility window for the private challenge, that the opponent's next play call accepts it, and that house fallback applies otherwise. It does not describe what the caller sees while waiting or the accepted-match response.

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 compact sentences, front-loaded with the primary action and its fallback, with auth tucked at the end. Dense but each sentence carries decision-relevant information, though the auth sentence slightly duplicates the schema.

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?

For a 6-parameter, zero-required matchmaking tool with no output schema and text-annotations, the description covers the branching logic, timing window, fallback behavior, and auth requirement. It could go further on what a successful match returns, but it is broadly adequate.

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 100%, so the schema already documents key, ref, game, mode, clock, and target in detail. The description reinforces the auth-header-vs-key precedence but adds little semantic meaning beyond what the parameters already state, so baseline 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 states specific actions and resources: call out a target, send a private challenge, or fall back to joining the open queue. However, it does not distinguish itself from siblings like pit_callout or pit_queue, which appear to overlap with its first and third branches, so an agent cannot cleanly separate this umbrella entry point from those specialized tools.

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 conditional guidance - pass a target to call out/challenge, otherwise the open queue is used with house fallback. What's missing is direction about when to prefer this consolidated tool over the dedicated pit_callout or pit_queue siblings.

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