Get tournament participants

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

The readOnlyHint annotation already declares the safe read-only nature, so the bar is lower. The description adds context by clarifying that these are tournament-level registrations (not per-event) and that the results include gamer tags, which is helpful beyond the annotation but not extensive. No contradiction.

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?

Two sentences with no wasted words. The primary purpose is stated first, and the crucial usage distinction is delivered in the second sentence. Well-structured and front-loaded.

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 read-only list tool with a fully documented schema and a readOnlyHint annotation, the description covers the core need: what it lists and when to use it instead of get_event_entrants. It does not mention pagination or return format, but those are inferable from the schema (page/perPage) and the read-only nature, making minor gaps.

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 100%, so the description need not repeat parameter details. The description does not add additional parameter guidance beyond what the schema provides, so the baseline of 3 is appropriate.

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 explicitly states the operation 'List' and the resource 'tournament's registered participants (attendees) with gamer tags', and differentiates it from the sibling get_event_entrants by noting the tournament-level scope. This is a clear, specific action and resource with sibling distinction.

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 this tool versus get_event_entrants: 'these are tournament-level registrations; for per-event entrants with seeding, use get_event_entrants instead.' This provides clear when-to-use and alternative guidance.

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