faceit_searchPlayers

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

No annotations provided, so description carries full burden. Describes endpoint, parameters, and return type; mentions fuzzy search but lacks details like case sensitivity or pagination limits beyond offset/limit. Still provides good transparency for a search tool.

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?

Concise, well-structured: usage hint, endpoint, parameter list, return statement. No wasted words; every sentence adds value.

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?

With 5 parameters, 1 required, and no output schema, description covers key aspects: fuzzy search, all parameters, and return type. Could specify more about expected output structure, but adequate for its complexity.

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 description compensates well. Lists all parameters with type, constraints, optionality, and return value. Game and country descriptions are minimal but functional.

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 'Search for players' with 'fuzzy nickname search', and explicitly distinguishes from sibling tools getPlayerFromLookup (exact nickname) and getPlayer (by player_id).

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?

Explicit guidance: 'Prefer getPlayerFromLookup when the nickname is exact, or getPlayer when you already have the player_id.' This tells the agent when to use this tool vs alternatives.

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