igdb_get_game

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

No annotations provided; description says "Get full details" implying read-only, but fails to disclose authentication (client_id, client_secret are required) or any error behavior (e.g., if game_id is invalid).

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?

Single sentence of 12 words, very concise but missing critical details; balance between brevity and completeness could be improved.

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?

No output schema; description does not explain what "full details" includes, leaving agent unaware of response structure. Lacks context on authentication flow and edge cases.

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 only 33% with description only for game_id; client_id and client_secret are left undescribed, and the description adds no extra meaning beyond parameter names.

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?

Description uses specific verb "Get" and resource "full details of a game from IGDB by game ID", clearly differentiating from sibling igdb_search_games which returns search results.

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?

Description implies you need a known game ID, but does not state when to use this versus igdb_search_games, nor mention prerequisites or exclusions.

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