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

The description adds no behavioral context beyond what the annotations already declare (readOnlyHint=false, destructiveHint=false, etc.). It does not explain that this mutates the game state, whether it requires an active match, or what happens on success. Since annotations are minimal and the description carries the burden, this is a significant gap.

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 a single sentence with no wasted words, but it is under-specified. It is concise but lacks the structure that would highlight key information. A 3 reflects that it is not verbose, but it also does not provide adequate information in a well-organized way.

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 2 parameters, no output schema, and minimal annotations, the description should provide more context about prerequisites, side effects, or typical usage. It does not mention that the match must be ongoing, what constitutes a valid draw offer, or what happens after the action. This is insufficient for an agent to invoke it confidently.

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 50% (only match_id has a description). The action parameter has an enum but no explanation of what each value does in context. The description does not compensate by explaining parameter meanings or relationships, leaving the agent to infer from the enum alone.

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 a specific verb (offer/accept/decline) and a resource (draw), which clearly indicates the tool's purpose. However, it does not distinguish it from sibling tools like pit_resign or pit_move beyond the draw-specific action, so it misses the sibling differentiation that would earn a 5.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention conditions like 'when a draw is offered to you' or 'when you want to propose a draw', nor does it reference any sibling tool. The description gives no context for selection.

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