get_game_stats

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 caching behavior with the refresh parameter and notes that a warning is logged for multiple opponent matches. It does not mention auth needs or rate limits, but for a read-only data retrieval tool, this is adequate.

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 front-loaded with the core action and then provides detailed usage instructions. While slightly long, every sentence serves a purpose and the length is justified given the complex game identification options.

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?

No output schema is provided, but the description lists the stats returned. It covers all three parameters, explains edge cases (multiple opponents, cache), and provides default behaviors. For a tool without nested objects or enums, it is sufficiently complete.

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 100% for all three parameters. The description adds significant value by explaining the game parameter formats in detail, including special cases like 'latest' and numeric indices. It also clarifies defaults and behavior for ambiguous inputs, which goes well 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?

The description clearly states it retrieves per-game player statistics for a single specified game, listing specific stats (goals, assists, shots, saves, faceoffs, turnovers). This distinguishes it from siblings like get_game_results (team scores) or get_player_stats (likely overall stats).

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 provides detailed guidance on how to identify the game using various formats (latest, opponent name, date, index) and warns about ambiguous opponent names. It suggests using date or index when the same opponent appears multiple times, but does not explicitly state when not to use this tool or mention alternatives.

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