Get Recently Played Steam Games

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the basic function without disclosing authentication requirements, caching behavior, rate limits, or the meaning of 'recently' (e.g., time range). The presence of an output schema does not compensate for missing safety or side-effect information.

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 a single sentence with no wasted words, achieving maximum conciseness. However, it is too brief to convey necessary details, and the structure does not front-load critical information like parameters or usage notes. It balances brevity and informativeness poorly.

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 has two parameters, no annotations, but an output schema, the description is incomplete. It does not explain parameter semantics, usage context, or behavioral notes like caching. For a tool with many siblings, more contextual detail is needed to enable correct invocation.

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 has 0% description coverage for its two parameters (count, forceRefresh). The description does not mention or explain these parameters, failing to add meaning beyond the raw schema. An agent cannot determine the effect of each parameter without external knowledge.

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 verb 'Get' and the resource 'recently played Steam games', indicating the tool retrieves a user's recently played games. However, it lacks differentiation from sibling tools like steam_get_owned_games or steam_get_installed_games, which could cause confusion for an AI agent choosing between them.

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 provides no guidance on when to use this tool versus alternatives. There are no usage restrictions, prerequisites, or examples of appropriate contexts, leaving the agent without decision-making support.

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