search_game

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

No annotations are provided, so the description must disclose behavior itself. It reveals that the search returns up to 10 matches with IDs, which is useful for understanding the output. It doesn't explain matching semantics, pagination, or error states, but the note about passing IDs to get_game/get_game_reviews offers practical behavioral context that goes beyond a bare search definition.

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 two sentences long, with the function stated immediately. The second sentence provides essential output information without unnecessary elaboration. It is concise and well-structured.

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?

The tool is simple with one parameter and no output schema, but the description conveys the essential context: the result format (up to 10 matches with IDs) and how to use those results with sibling tools. This makes it complete for an agent to know when to use it and what to expect, despite the absence of an output schema.

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?

The schema already fully describes the only parameter 'query' with examples, so the schema coverage is 100%. The description adds no further parameter details beyond what's already in the schema. Therefore, no extra value is added from the description for parameter understanding.

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's function: 'Search for a game by name on OpenCritic.' The verb 'search' and the resource 'game by name' make it distinct from sibling tools like get_game and get_game_reviews, which are presumably for fetching specific details or reviews once an ID is known.

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 this tool: when you have a game title but need its OpenCritic ID. It explicitly states the IDs 'can be passed to get_game or get_game_reviews,' which guides the follow-up workflow. However, it doesn't explicitly say 'use this instead of X' or provide exclusion criteria.

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