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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses that signed-in players are notified by email, which is a meaningful side effect. It also notes the cap-related behavior, adding context not available in the structured data. No contradiction with annotations.

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 only two sentences, front-loaded with the main action, and every word contributes value. It avoids repetition of schema details and stays focused on the tool's purpose and key context.

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?

The tool is relatively simple, and an output schema is provided, so return values are covered elsewhere. The description addresses the core scenario, the email notification, and the cap alternative. It doesn't discuss edge cases like failure modes, but those are not essential given the tool's simplicity and the presence of other structured context.

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 67% (tournament_key and request_id have descriptions). The description doesn't explicitly explain the `name` parameter, which lacks a schema description, but the tool's purpose implies it identifies the waitlisted player. Overall, the description adds minimal parameter-level semantic value 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?

The description clearly states the action ('Move a waitlisted player onto the active roster') and the specific condition ('when a spot opens'). It distinguishes itself from sibling tools like add_players, remove_player, and replace_player by focusing on the waitlist-to-active roster transition.

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 provides a clear trigger ('when a spot opens') and suggests an alternative for a related scenario ('The cap can be raised with update_settings'). It doesn't explicitly exclude other player-management tools, but the context is sufficient for an agent to know when to choose this tool.

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