Get a game's full achievement list

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

Adds value beyond annotations: mentions the 200 cap, check returned vs total, API key requirement, and what fields are returned. No contradiction with readOnlyHint=true and openWorldHint=true.

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?

Front-loaded with core purpose, then provides usage context and alternatives in a compact three-sentence structure. No extraneous information.

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 output schema exists, description covers return fields, cap, and pagination hint (returned vs total). Also includes prerequisites and sibling links. Complete for a filtered list 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 coverage is 100% with descriptions for both parameters. The description adds no new parameter info beyond reiterating appid source and the cap (which is behavioral, not param-specific). Baseline 3 is appropriate as schema does the heavy lifting.

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 specifies the verb (list), resource (game achievements), and detailed output (names, descriptions, hidden flag, global unlock %, order). It clearly distinguishes from siblings by naming alternatives, so an agent can select the correct tool.

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?

Explicitly states when to use alternatives (get_global_achievements, get_game's achievements_highlighted, get_player_achievements) and requires STEAM_API_KEY. No ambiguity about context.

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