faceit_getTournamentMatches

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

No annotations are provided, so the description carries the burden. It discloses the endpoint, parameters, and return type (Matches list), but lacks details on error handling, authentication, or whether it is read-only (likely).

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 concise (6 lines) with clear sections: purpose, usage, endpoint, parameters, and return. Every sentence serves a purpose with no redundancy.

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 the simple parameters and no output schema, the description covers the necessary details: what it does, how to use it with pagination, and what is returned. Could mention match list structure, but not required for completeness.

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%, but the description adds significant value by specifying parameter types (path/query), constraints (min/max for offset and limit), and required status, beyond the schema's title and type only.

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 tool retrieves all matches of a tournament using specific verbs like 'Retrieve' and 'list', and distinguishes from sibling tools like faceit_getMatch (single match) and faceit_getChampionshipMatches (championship matches).

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 says 'Use to list all matches of a known tournament', implicitly requiring a known tournament_id. It is clear but does not explicitly exclude alternatives or provide when-not scenarios, though it differentiates well from siblings.

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