faceit_getTournamentsList

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

No annotations provided, so description carries full burden. It discloses deprecation and endpoint, but does not mention any side effects, auth requirements, rate limits, or output behavior beyond 'Returns: Tournaments list'. For a simple read operation, this is adequate but minimal.

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?

Well-structured with deprecation notice, alternatives, endpoint, and parameter list. Concise but could be slightly more compact by combining deprecation and alternative recommendation. No wasted sentences.

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 it's a deprecated list tool with no output schema, the description covers purpose, usage, and parameters. It does not explain return format or pagination, but the context is sufficient for correct invocation.

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?

Parameter descriptions are detailed in the description text, even though input schema property descriptions are empty (0% coverage). Each parameter (game, region, offset, limit) includes type, default, and constraints. Adds significant 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?

Clearly states it retrieves tournaments (v1) and explicitly mentions deprecation. The verb 'Retrieve' combined with 'tournaments v1' and the endpoint makes purpose unambiguous. Differentiates from siblings by noting it's deprecated and suggesting alternatives.

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?

Explicitly states to prefer alternatives: searchTournaments, getOrganizerTournaments, or getTournament as appropriate. This provides clear guidance on when not to use this tool and which tools to use instead.

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