Get Recently Played Games

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

No annotations provided; description only mentions timeframe and playtime breakdown. Missing details on return format, auth requirements (beyond Steam ID), rate limits, or whether games are only those with playtime >0.

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?

Single sentence of 14 words, front-loaded with key information, no wasted words. Highly efficient.

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 simple tool with 1 param and no output schema, description is adequate but lacks hint about return format (e.g., list of games). Does not clarify if timeframe is fixed or relative.

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 value by explaining the parameter is a 64-bit Steam ID and noting the fallback to STEAM_ID env var, which helps agents understand optional behavior.

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 resource (games a player has played), timeframe (last two weeks), and output (playtime breakdown). It distinguishes from siblings like get_owned_games and get_player_achievements.

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 vs alternatives. With 19 sibling tools, the description should indicate different use cases, e.g., comparing with get_owned_games.

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