get_steam_achievements

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

No annotations are provided, and the description only states the basic purpose. It does not disclose output format, authentication requirements (api_key parameter is optional but not explained), or any potential side effects or limitations.

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 a single concise sentence with no unnecessary words. However, it could be structured to include more information without verbosity, such as noting required parameters.

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 the absence of output schema and annotations, the description is too brief to fully inform the agent. It does not describe the response structure (e.g., list of achievement objects) or any pagination, making it incomplete for a tool that returns a list of achievements.

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?

The input schema has 67% description coverage (steamid and appid have descriptions, api_key does not). The tool description does not add any extra meaning beyond the schema's brief descriptions; it does not explain how to obtain a Steam64 ID or App ID.

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 retrieves achievements for a Steam user in a specific game, using a specific verb and resource. It differentiates from sibling tools like get_steam_player_summaries and get_steam_owned_games.

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?

No guidance on when to use this tool versus alternatives like get_steam_app_details or get_steam_owned_games. The description does not explain prerequisites such as requiring a valid Steam64 ID and App ID.

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