Get recently played Steam games

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

Annotations already declare readOnlyHint=true, so the description adds context about including total playtime, which is useful. However, it does not disclose edge cases like empty results, error handling, or rate limits. For a read-only tool with annotations, the behavior is adequately but minimally transparent.

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 two sentences, with the first sentence stating the core functionality and the second noting prerequisites. Every sentence adds value; no filler or repetition. It is front-loaded and appropriately sized.

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 zero schema documentation for parameters, no output schema, and 2 parameters, the description is insufficient. It does not explain pagination (limit/offset), return structure, or behavior when no games are recent. The tool's complexity is low but the gaps are critical for correct usage.

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 description coverage is 0%, and the description does not mention the two parameters ('limit' and 'offset'). It fails to compensate for the lack of schema descriptions. The agent has no guidance on how to paginate or cap results.

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 states 'Get games Steam reports as recently played, including total playtime.' The verb 'Get' and resource 'recently played Steam games' are specific. This distinguishes the tool from siblings like 'steam_get_library' which lists all games, and 'steam_find_game' which searches.

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 mentions required environment variables (STEAM_API_KEY and STEAM_ID), implying prerequisites. However, it does not explicitly state when to use this tool versus alternatives like 'steam_get_library' for all games or 'steam_search_store' for store searches. Usage context is implied by 'recently played' but not elaborated.

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