Search Steam Library

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. It fails to mention whether the tool returns game IDs, names, or full details, nor does it discuss caching, performance, or any side effects. The single sentence is insufficient.

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 short, it omits essential information such as parameter semantics and response format. True conciseness preserves clarity without losing necessary details; this version is under-specified.

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 complexity of 4 parameters and the existence of an output schema, the description is severely incomplete. It does not explain what the output contains, how fuzzy matching works, or any constraints like rate limits or prerequisites.

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 schema has 0% description coverage and the description adds no meaning for the four parameters (limit, query, forceRefresh, includeInstalledStatus). The agent is left to guess their semantics (e.g., what does forceRefresh do?; how does includeInstalledStatus affect results?).

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 explicitly states the verb 'search', the resource 'my owned Steam games', and the method 'by fuzzy name/query'. This clearly distinguishes it from sibling tools like steam_get_owned_games (which lists all owned games) or steam_get_game (which fetches details for a specific game).

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_get_owned_games for exact retrieval or steam_find_deals for deals. The description lacks context for appropriate usage scenarios.

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