get_recently_played

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

No annotations are provided, so the description must disclose behavior itself. It adds the temporal window ('last 2 weeks') and interpretive context ('strongest signal for mood and taste'), but it does not explicitly state that this is a read-only operation, nor does it mention return format or any side effects. The read-only nature is implied but not stated.

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 zero filler. The first sentence front-loads the core function, and the second provides actionable usage guidance. Every word adds value.

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 single-parameter read tool, the description covers purpose and usage context effectively. It lacks an explicit read-only declaration and output format details, but these are less critical given the tool's simplicity and the presence of usage guidance.

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 steam_id parameter at all. While the parameter name is self-explanatory, the description fails to compensate for the lack of schema documentation, leaving semantics like requiredness and intended owner unclear.

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 the tool returns 'Games played in the last 2 weeks', which is a specific verb+resource combination. It distinguishes itself from siblings like get_library and get_wishlist by focusing on recent activity as a mood/taste signal.

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 explicitly says 'Call this before recommend_from_library to understand recent preferences', providing unambiguous sequencing and a named alternative tool. This gives clear when-to-use guidance.

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