igdb_lookup_by_steam_appid

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

With no annotations, the description carries the full burden. It discloses the caching behavior (force_refresh overwrites cached results) and the per-call limit of 50 appids. It does not mention authentication, rate limits, or error handling, but these are secondary for a simple lookup and the core behavior is addressed.

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 compact and front-loaded, with the core purpose in the first sentence and parameter details in a clear, minimal list. There is no redundant or filler content.

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 tool's simplicity and lack of an output schema, the description provides sufficient context: input parameters, output format (id+name), caching behavior, and call limit. It does not detail edge cases like an appid with no IGDB match, but for a simple lookup this is acceptable.

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 coverage is 0%, so the description is the only documentation for parameters. It explains 'appids' as Steam appids with a max of 50, and 'force_refresh' as a flag to re-query IGDB and overwrite cache. This adds meaning that the schema's bare types lack, fully covering both parameters.

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 verb 'Map' and the specific resource (Steam appids to IGDB games) and output (id + name). It distinguishes itself from sibling tools like igdb_search_games (search by name) and igdb_get_game_details (get by IGDB id) by focusing on the Steam-to-IGDB bridge.

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 when to use the tool ('bridges a Steam library to IGDB metadata') and notes the maximum of 50 appids per call. However, it does not explicitly contrast with alternatives (e.g., when to use igdb_search_games instead) or state what happens when an appid has no match.

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