Search video games

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

Lacking annotations, the description only mentions 'using IGDB by default' but does not disclose pagination, result format, authentication, or rate limits. Minimal behavioral context beyond the source parameter.

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 short sentence, which is concise but lacks necessary detail. It is front-loaded but at the expense of completeness.

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?

With 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain search behavior, pagination, or the role of the source parameter, leaving the agent uncertain about expected results.

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 does not explain any of the four parameters (query, page, source, allowGamesWithParent). The mention of IGDB is implied but not explicitly connected to the source enum. Agent cannot infer parameter meanings from description alone.

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 searches video games in Ryot using IGDB by default. It identifies the resource (video games) and the action (search), but does not distinguish from siblings like ryot_search_media or ryot_game_discovery.

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 on when to use this tool versus alternatives like ryot_search_media or ryot_game_discovery. No context on prerequisites or exclusions.

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