Recently played games

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

No annotations are present, so the description must carry the behavioral burden. It does disclose the sort order ('newest first') and the temporal scope, but it does not explicitly state that the operation is read-only, nor does it describe the return shape or any 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?

The description is extremely concise and front-loaded: 'Games played recently, newest first' packs the resource and ordering in eight words with no filler. 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?

For a simple list tool with one optional parameter, the description is nearly enough: it tells the domain and order. However, with no annotations and no output schema, it leaves the read-only nature, the list return type, and the limit behavior implicit, making it minimally viable rather than fully complete.

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 only parameter, limit, is documented in the schema with type, default, minimum, and maximum, but the description does not mention it at all. With schema description coverage at 0%, the description was expected to compensate and explain how limit affects the result set, but it does not.

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 identifies the resource (recently played games) and adds the ordering detail 'newest first.' It is distinguishable from siblings like steam_library_list or steam_game_details by the 'recently played' scope, though it lacks an explicit verb such as 'List' or 'Retrieve.'

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 is given about when to use this tool over alternatives such as steam_library_list or steam_library_search. There are no stated exclusions, prerequisites, or context signals to help an agent choose between this and the many sibling tools.

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