Get Player Achievements

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

With no annotations provided, the description carries the full burden. It discloses that the tool reads achievement progress and returns unlock status and timestamps, indicating a read-only operation. However, it does not mention authentication requirements, rate limits, or whether the player's profile must be public.

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, clear sentence with no redundant words or fluff. It efficiently conveys the core functionality.

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 tool's simplicity and the presence of sibling tools, the description covers the main aspects. However, it lacks details about response format, potential prerequisites (e.g., public profile), or data freshness. Without an output schema, these details would be helpful for context.

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 already describes both parameters (app_id and steam_id) with 100% coverage. The description adds minimal value beyond restating that it's for a specific game and player. Baseline of 3 is appropriate as the description does not significantly enhance understanding of parameter meaning.

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 specifies the verb 'get' and the resource 'a player's achievement progress for a specific game', including the type of data returned (unlocked achievements and timestamps). It effectively distinguishes from sibling tools like 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?

The description does not explicitly state when to use this tool over alternatives or when not to use it. While the purpose implies usage for individual achievement progress, no guidance is given for choosing among similar sibling tools like get_user_stats_for_game or get_global_achievement_percentages.

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