rawg_game_screenshots

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

No annotations are provided, so the description carries full burden. It does not disclose that the operation is read-only, whether authentication is required (the 'api_key' parameter suggests it), or any behavioral aspects like rate limits or response size. The single sentence adds no behavioral context beyond the tool's name.

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 concise (one sentence) but overly terse. It lacks structure; key information like parameter details or return format is missing. While brevity is good, it sacrifices usefulness for the agent.

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 (2 parameters, no output schema), the description is incomplete. It does not hint at the return format (e.g., list of screenshot URLs) or any constraints like pagination. The agent cannot fully understand the tool's behavior from this description alone.

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 0%, and the description adds no meaning to the parameters. It does not explain that 'id' is the game ID or how to obtain it, nor does it clarify the 'api_key' parameter's purpose or optionality. The description fails to compensate for the lack of parameter documentation.

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 tool retrieves screenshots for a RAWG game, with a specific verb ('Get') and resource ('screenshots for a RAWG game'). It distinguishes itself from sibling tools like 'rawg_get_game' or 'rawg_search_games'. However, it lacks detail on what exactly is returned (e.g., all screenshots or a subset), which slightly reduces clarity.

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 explicit guidance on when to use this tool vs. alternatives. The description does not mention when not to use it, nor does it differentiate usage from siblings like 'rawg_get_game' or 'rawg_search_games'. The context is implied but not stated.

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