Get a player's achievements

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

Annotations already declare readOnlyHint and openWorldHint, so description adds value by specifying auth requirements (public profile) and return data details. No contradictions.

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?

Two sentences, front-loaded with key action and output, no fluff. Second sentence adds critical auth condition.

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 tool with 3 params and no output schema, the description explains purpose, return data, auth requirement, and parameter usage. References to other tools aid completeness. Could cover error cases but not missing essential info.

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%, but description adds meaning: mentions steamid is optional and can be omitted to use configured STEAM_ID, language overrides STEAM_LANGUAGE, and references other tools for conversion (resolve_vanity_url).

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 the tool gets a player's achievement progress for one game, listing specific data returned (unlocked count, % complete, per-achievement unlock dates) and inputs (SteamID64 + appid). It distinguishes from sibling get_game_achievements which is likely global.

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 mentions requirement of STEAM_API_KEY and public profile, providing usage context. However, it does not explicitly state when not to use this tool or mention alternatives like get_game_achievements for global stats.

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