Get Owned Steam Games

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get my owned Steam games' only states the action but does not reveal whether it requires authentication, the nature of the operation (read-only), any side effects, or performance implications.

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?

While the description is concise at one sentence, it is too sparse to be useful. It sacrifices essential context for brevity, resulting in under-specification rather than efficient communication.

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 6 parameters with zero documentation and no output schema description, the description is grossly incomplete. The agent lacks information on how to customize the query or interpret the results.

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 does not mention any of the 6 input parameters (limit, sortBy, forceRefresh, sortDirection, includeAppInfo, includeFreePlayed). With 0% schema description coverage, the agent receives no guidance on how to use these parameters or what they control.

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 'Get my owned Steam games' is nearly identical to the title and tool name, making it a tautology that adds no new information. It fails to specify the scope or distinguish from siblings like steam_get_installed_games or steam_get_recently_played.

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?

No guidance is provided on when to use this tool versus alternatives such as steam_search_library or steam_get_wishlist. There are no hints about prerequisites, when-not to use, or which sibling tools might be more appropriate.

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