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

Annotations declare destructiveHint=true and idempotentHint=true; the description adds meaningful consequence detail the annotations don't carry — the queue-vs-forfeit distinction, the public loss record, and that the seat closes. It does not describe return values or error behavior, but the destructive side effects are well disclosed.

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?

Front-loaded with the action, then consequences, then the closing instruction — no wasted sentences. The telegraphic fragments are efficient, if slightly choppy.

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 destructive, no-output-schema mutation with fully documented params, the description covers the essential behavioral consequences an agent needs. Only minor gaps remain (exact failure modes, whether a pass being absent blocks the call despite zero required params).

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 the pass and pilotKey semantics are already fully documented in the schema. The description's 'Send pass' merely reinforces that a pass accompanies the call; it adds no format or conditional detail 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?

Opens with a specific verb+resource ('Leave the match'), which is unambiguous and clearly distinct from siblings like send_command, take_command, and act. It lacks explicit naming of an alternative for related intents, but the action is unmistakable.

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?

Gives concrete context for when this applies and what it means at each stage: while waiting for a foe it 'only leaves the queue', afterward it is 'a forfeit and a loss'. That is effectively a when-to-use / what-it-costs rule, though it doesn't compare against siblings.

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