get_steam_achievements

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

With no annotations provided, the description must fully disclose behavioral traits, but it only states the action 'Get achievements'. It does not confirm read-only behavior, mention authentication requirements (despite api_key being optional), or describe rate limits or error states. This is insufficient for a tool with no annotations.

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 efficient sentence with no unnecessary words. It is front-loaded and easy to parse. However, it sacrifices informativeness for brevity, missing opportunities to add value without losing conciseness.

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?

There is no output schema, so the description should clarify the return format (e.g., list of achievement objects). It does not mention possible errors (e.g., invalid steamid, appid mismatch) or pagination. Given the tool's moderate complexity (3 params, no output schema), the description is incomplete.

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 schema description coverage is 67% (steamid and appid have descriptions, api_key does not). The description adds minimal meaning beyond the schema by linking 'Steam user' to steamid and 'specific game' to appid, but does not explain the api_key parameter. Baseline 3 is appropriate as schema does most of the work.

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. It uses a specific verb and resource, and the purpose is distinct from sibling tools like get_steam_app_details or get_steam_owned_games. However, it does not explicitly differentiate itself from these siblings.

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 no guidance on when to use this tool versus other Steam-related tools. It lacks context about prerequisites, such as requiring the user to own the game, and fails to mention alternatives like get_steam_owned_games for verifying ownership.

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