Get Game Schema

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

No annotations; description indicates read-only operation without stating so explicitly. Lacks disclosure of side effects, error handling, or authentication needs. Adequate for a simple retrieval but not detailed.

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?

Single sentence, 18 words, no redundancy. Front-loaded with key action and resource. Efficient and clear.

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 and no output schema, description covers essential output content (stats, achievements, details). Could add note about scope (full game schema vs player-specific). Mostly 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?

Single parameter app_id is well-documented in schema with 100% coverage. Description adds no extra semantics beyond confirming 'game' context. Baseline score of 3 applies.

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?

Description clearly states verb 'Get' and specific resource 'full list of stats and achievements', including details like display names, descriptions, and icons. Distinguishes from siblings like get_player_achievements and get_global_achievement_percentages.

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?

Implies usage for retrieving achievements/stats, but no explicit guidance on when to use vs alternatives like get_game_details or get_player_achievements. No exclusions or prerequisites stated.

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