Get recently played games

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so description adds value by disclosing authentication requirements, profile visibility constraint, and the found:false failure mode. Could be improved by noting that it returns recent playtime data with no side effects.

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 with no wasted words. First sentence states purpose and scope, second gives alternative and requirements. Front-loaded and 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?

Given the simple input (1 optional parameter), presence of output schema, and annotations providing safety profile, the description covers all necessary context: purpose, usage guidelines, prerequisites, failure mode, and sibling differentiation. Complete for effective agent use.

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?

Input schema has 100% coverage for the single steamid parameter with pattern and description. Description adds important usage context: omitting uses configured STEAM_ID, and advises converting vanity URLs with resolve_vanity_url first, which goes beyond schema.

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 uses a specific verb ('List') and resource ('games a player has played in the last two weeks') with clear scope (time frame) and differentiates from sibling tool get_owned_games, which covers all-time top 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?

Explicitly states when to use this tool vs get_owned_games ('For all-time top games by playtime instead... use get_owned_games') and mentions prerequisites (STEAM_API_KEY, public profile with game-details visibility) and failure condition ('returns found:false').

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