get_steam_owned_games

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

No annotations are provided, so the description carries the full burden. It only states basic functionality without disclosing that the tool is read-only, requires authentication, or any side effects. The api_key parameter hints at auth but is not mentioned in the description.

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 conciseness. However, it lacks structure such as a summary of required parameters or authentication hints that would improve usability without adding bulk.

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 no output schema and four parameters (some with no schema descriptions), the description is incomplete. It does not explain return value format, authentication requirements, or parameter effects, leaving an AI agent without enough context to use the tool effectively.

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 50% (2 of 4 parameters have descriptions), and the tool description adds no additional parameter information. For parameters like include_played_free_games and api_key, which lack schema descriptions, the description offers no help, failing to compensate for the low coverage.

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 action 'Get' and the resource 'games owned by a Steam user', making the tool's purpose unambiguous. It distinguishes itself from sibling Steam tools like get_steam_achievements or get_steam_app_details by specifically targeting owned games.

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 implies usage for retrieving owned games but offers no explicit guidance on when to use this tool versus other Steam tools or what prerequisites exist (e.g., need for API key). Alternatives are not mentioned, though context with sibling tools provides some differentiation.

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