steam_get_owned_games

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it includes total and recent hours, but does not disclose default behaviors such as using the configured Steam user, including free games, or pagination behavior. This is acceptable but not rich.

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 filler, directly stating the action and output. It is front-loaded and 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 read-only listing operation with well-documented parameters and an output schema, the description is minimal but adequate. It lacks notes on authentication, private profiles, or rate limits, but these are less critical given the annotations and schema richness.

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 description mentions no parameters directly, but the input schema provides full descriptions for all parameters (limit, offset, sort_by, steamid, response_format, include_free_games). With schema coverage at 100%, the baseline of 3 applies; the description adds no extra semantic meaning.

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 uses the specific verb 'List' and clearly identifies the resource ('games a user owns') with details about the output ('total and recent hours played'). This distinguishes it from siblings like steam_get_recently_played_games, which focuses on recent play sessions rather than the full library.

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 such as steam_get_recently_played_games or steam_analyze_library. It also doesn't mention prerequisites (e.g., Steam API key) or exclusions, which is important given the broad sibling set.

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