faceit_getPlayerTeams

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

No annotations provided. The description includes the HTTP method (GET) implying a safe read, but does not explicitly state read-only nature, authentication needs, or rate limits. It adds basic transparency via endpoint information but lacks deeper behavioral context.

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 efficiently structured: one-line purpose, usage hint, endpoint, parameter list, and return statement. No redundant information; front-loaded with key action.

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 a simple list retrieval, the description mentions 'Returns: Teams of a user' which is adequate but could elaborate on the structure of team objects. It is mostly complete for a straightforward tool.

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 compensates fully by listing each parameter (player_id, offset, limit) with type, path/query, constraints, and purpose. This adds meaning 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 states 'Retrieve all teams of a player' and 'Use to list teams a player is a member of.' It clearly identifies the verb (retrieve/list) and resource (teams of a player), distinguishing it from sibling tools like faceit_getPlayer (player profile) or faceit_getPlayerHubs (hubs).

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 explicitly says 'Use to list teams a player is a member of,' indicating when to use. It does not provide when-not-to-use or alternative tools, but the context from sibling names makes it clear that this is the dedicated tool for teams.

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