steam_getOwnedGames

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

No annotations provided, so the description carries the burden. It discloses that it shows owned games, total playtime, and recent playtime, and requires an API key. However, it does not mention potential rate limits, error conditions, or the read-only nature of the operation.

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, with two succinct sentences. The first sentence conveys the core purpose, and the second adds a critical requirement. No wasteful words.

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 absence of annotations and output schema, the description reasonably covers the tool's behavior and requirements. It could be improved by mentioning that steamid is required (though schema covers it) or listing typical output fields.

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 already has 100% coverage, describing each parameter (steamid, include_played_free_games, include_appinfo). The description adds no additional semantic meaning or usage details beyond what the schema provides.

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 retrieves a player's game library with playtime data, using specific verbs and resources. It distinguishes itself from siblings like steam_getPlayerSummary or steam_getPlayerAchievements by focusing on owned games and playtime.

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 a requirement (STEAM_API_KEY) but does not provide guidance on when to use this tool versus alternatives, nor does it specify conditions or exclusions. The context is implied but not explicit.

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