igdb_list_platforms

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 only states 'List gaming platforms' without mentioning read-only nature, authentication requirements, rate limits, or any side effects. This is insufficient for a tool that requires client credentials and presumably makes external API calls.

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 wasted words, but it is under-specified. While concise, it sacrifices informativeness. It could benefit from additional context without becoming verbose.

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 has no output schema, no annotations, and poor parameter documentation, the description is too sparse. It does not explain the return format, authentication flow, or pagination (despite having limit and offset). The agent would struggle to use this tool correctly without external knowledge.

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 description coverage is only 25% (only 'limit' has a description). The tool description does not add any meaning to the parameters beyond what the schema provides. It fails to explain the purpose of 'offset', 'client_id', or 'client_secret', which are critical for usage. The description does not compensate for the low coverage.

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 action ('List'), the resource ('gaming platforms'), and the source ('from IGDB'). It effectively distinguishes from sibling tools like igdb_search_games (search) and igdb_list_genres (list genres), providing a specific, unambiguous purpose.

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 vs alternatives (e.g., rawg_list_platforms). There is no mention of prerequisites, scenarios where it is preferred, or when not to use it. The agent lacks context for appropriate selection.

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