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

Annotations already declare readOnlyHint and idempotentHint, so the description does not need to restate those. It adds valuable behavioral context by stating 'Nothing is stored' and by specifying exactness conditions for fields in fours versus 'fair sit-outs otherwise.'

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 short sentences deliver the core purpose, behavioral guarantees, and persistence semantics with no filler. The most important information is front-loaded before the fairness details.

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 stateless, read-only generator with optional parameters, the description covers purpose, player range, schedule properties, and non-persistence. It does not explicitly describe the output format, but the phrase 'rounds of rotating-partner doubles' strongly implies the return value, and the schema covers the remaining parameter details.

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 schema already documents seed, courts, rounds, and players, while the description adds context about 'players−1 rounds' and fairness behavior linked to player count. However, it does not clarify the meaning of names, format, or courts beyond what the schema provides, and schema coverage is only 67%.

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 title supplies the verb 'Generate' and the description names the resource: 'rounds of rotating-partner doubles for 4 to 64 players.' This clearly identifies what the tool produces and is not confusable with the listed siblings, none of which involve schedule generation.

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 description explains what the tool does but gives no guidance on when to choose it over alternatives, nor any explicit context such as prerequisites or exclusions. The only usage signal is the implicit one from the title, which is weak.

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