Accept matchmaking ready check

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is partly covered. The description adds meaningful context beyond the annotations: it names the specific endpoint that must be write-allowlisted ('POST /lol-matchmaking/v1/ready-check/accept') and clarifies the no-op behavior when no ready check is active. It does not describe rate limits or return values, but the annotations carry the core behavioral burden here.

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 front-loaded with the core action and then routes to alternatives. It is appropriately sized for a zero-parameter workflow tool. A minor point: the sentence about the write allowlist endpoint is useful but slightly operational; overall there is no significant waste.

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?

Given that this is a zero-parameter, annotation-rich tool with no output schema, the description provides what an agent needs: purpose, usage conditions, alternatives, safety behavior, and a critical operational prerequisite (the allowlisted endpoint). It is nearly complete, though it could have mentioned whether it returns a confirmation or relies on side effects, but no output schema exists so that is a minor 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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameter syntax and correctly avoids inventing any. It does add context about the state dependency (no-op if no ready check is active), which is useful even though it is not a parameter.

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 (accepts) and resource (matchmaking ready check), and distinguishes itself from siblings by naming lol_workflow_lobby and lol_workflow_champ_select as the correct tools for adjacent workflow steps. An agent can tell exactly what this tool does versus the other lol_workflow_* 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 explicitly states when to use it ('during queue pop', 'when automated match acceptance is needed') and when not to use it, naming two alternatives and the exact cases they cover. The directive to prefer this over manual REST calls or lol_eval removes ambiguity.

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