Get recently played games

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

Annotations already mark readOnlyHint and openWorldHint. Description adds context that profile must be public, which is valuable beyond annotations. No contradictions or missing critical behaviors like error handling.

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, no redundancy. First sentence clearly states purpose and output. Second sentence covers requirements and parameter usage. Every word earns its place.

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?

No output schema, but description gives some idea of return fields (recent and total playtime). For a simple listing tool with 1 parameter, this is sufficient. Could mention potential error cases like private profiles, but not required.

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 has 100% coverage, but description adds significant meaning: optionality of steamid, fallback to server-configured ID, and suggestion to use resolve_vanity_url for vanity names. This exceeds schema documentation.

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 verb 'list', specific resource 'games a player has played', time frame 'last two weeks', and data returned 'recent and total playtime'. Distinguishes from siblings like get_owned_games (all owned) 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?

Includes prerequisites (STEAM_API_KEY, public profile) and parameter guidance (omit for configured ID, use resolve_vanity_url for custom URLs). Lacks explicit when-not-to-use relative to other siblings like get_owned_games.

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