Get recently played games

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

Beyond the readOnlyHint annotation, the description adds critical behavioral details: the 50-item cap with instruction to check returned vs total, ordering by playtime not recency, and the exact requirement for public profile with game-details visibility. It also discloses the found:false response on failure, giving the agent a clear picture of behavior.

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?

Three sentences, each earning its place: the first defines the core behavior and ordering/cap, the second provides the alternative tool, and the third covers prerequisites and failure behavior. No redundancy or fluff; information is front-loaded and well-structured.

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 an output schema, the description covers all essential context: behavior, ordering, cap, alternative, authentication requirement, and failure mode. It is fully complete for an agent to decide when and how to invoke the tool correctly.

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 fully documents the single steamid parameter with a detailed description including how to omit it and vanity URL conversion. The tool description adds no additional parameter semantics beyond implicit player context, so the baseline of 3 is appropriate given 100% schema coverage.

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 clearly states the resource: games a player has played in the last two weeks, including recent and total playtime. It also distinguishes itself from get_owned_games by explicitly noting the difference in time window and sorting, making its purpose unmistakable.

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?

Provides explicit when-to-use guidance by directing users to get_owned_games for all-time top games. It also states prerequisites (STEAM_API_KEY, public profile with game-details visibility) and the failure mode ('returns found:false'), which clearly indicates when this tool is appropriate.

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