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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add context beyond safety — which it does: it warns about access/delay/metered usage following the connected account, that an empty result must not be read as lack of coverage, that it is a single bounded request with no background polling or automatic retry, that Affiliate 27 is excluded, and that it is not for wagers or account changes. The only gap is no mention of pagination or output shape, but an output schema exists.

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 content is front-loaded with the core purpose and market-mapping rule, but the description runs long, mixing usage guidance, example URL, cross-endpoint chaining, behavioral disclaimers, and a no-wagers notice in a single block. It is dense rather than wasteful, but an agent reading in one pass may lose the routing thread.

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 tool with an output schema, the description need not describe return values, and it appropriately focuses on usage, chaining, and coverage caveats. The only missing piece is a note on pagination or result limits for a participant list, but given the output schema and the rich usage guidance, coverage is strong.

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 0%, so the description carries the full parameter burden. It explains that participant_id (from the response) should be used rather than the generic id for filtering, and it demonstrates event_id, market_ids, and participant_type syntax in the example URL. It does not separately document participant_ids or the exact comma-separated constraints, but the example and the id distinction are meaningful additions 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 states a specific verb (Get) and resource (market participants) plus the scope — teams, players, or result sides for a requested event and markets. It also names the sibling use case (filtering participant-specific charts via history endpoints), which no other sibling tool does, so an agent can distinguish it from v2GetMarketsByDate or v2GetPlayersByTeam.

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?

There is explicit when-to-use guidance ('Use participant_id from this response to filter a participant-specific chart'), a concrete worked example with a full URL, and the market-specific mapping rules (market 3 uses TYPE_RESULT, markets 1 and 2 use TYPE_TEAM). This is more than routing — it instructs how to chain the response into the correct history endpoint.

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