faceit_getParentGame

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

No annotations are provided, so the description carries the full burden. It discloses the endpoint and that it returns 'Game detail', but does not mention authentication, rate limits, or any side effects. For a simple read operation, it is adequate 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 fairly concise with separate sections for purpose, usage, endpoint, parameters, and returns. The 'Parameters:' block is redundant with the schema but overall structure is efficient.

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?

For a simple tool with one parameter, the description covers purpose, usage, endpoint, and return type. While 'Returns: Game detail' is vague, it is arguably sufficient given the tool's simplicity and the lack of an output schema.

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 coverage is 0%, so the description must compensate. It adds the endpoint format (path) and type (string, required) but only restates 'The id of the game'. It does not explain what constitutes a valid game_id or how to find it, providing minimal added meaning.

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's action: 'Retrieve the details of the parent game, if the game is region-specific'. It uses specific verb 'Retrieve' on resource 'parent game' and distinguishes from siblings like faceit_getGame which gets any game.

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?

Description explicitly states when to use: 'Use when the game_id is a region-specific variant...and you want the canonical parent game.' This provides clear context, though it does not explicitly state when not to use or alternatives.

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