faceit_getTournamentTeams

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

With no annotations, the description carries the full burden. It provides the endpoint, parameter details, and return type ('Teams list'), but lacks information about pagination behavior, rate limits, authentication requirements, or the structure of the returned list. Basic behavioral info is present but not rich.

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 well-structured with a purpose statement, endpoint, parameter list, and return type. It is concise, though the first two sentences are slightly redundant. Overall, it is efficient 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?

Given no output schema and no annotations, the description covers the essential information for using the tool (parameters, return type). However, the return type is vague ('Teams list'), and no details about the team object structure are provided. It is moderately complete but lacks depth for a fully autonomous agent.

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%, and the description manually lists parameters with explanations: tournament_id ('The id of the tournament'), offset ('starting item position'), limit ('number of items to return'), including min/max constraints. This adds significant semantic value beyond the bare 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 'Retrieve all teams of a tournament' and 'list teams registered to a known tournament', providing a specific verb and resource. It distinguishes from sibling tools (e.g., faceit_getTournament, faceit_getTournamentMatches) by focusing exclusively on teams.

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 teams registered to a known tournament', which implies when to use it. However, it does not explicitly mention when not to use it or provide alternatives. Given the clear name and context from sibling tools, the guidance is adequate but not fully explicit.

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