search_games

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

No annotations are provided, so the description must cover behavioral aspects. It explains the search action but does not disclose details like rate limits, pagination behavior, or multiple results. The limit parameter hints at pagination, but the description does not confirm.

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?

Two sentences with no extraneous words. Information is front-loaded with the action and context.

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 2 parameters and no output schema, the description gives the tool's purpose but does not specify the return format or how results are structured. The agent would need additional context to parse responses, but the siblings are distinct, so this may be sufficient as an entry point.

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 100%, so the parameters are already described. The description adds context that the search is by title and the goal is to get an ID, but it does not provide additional specifications like search algorithm (fuzzy vs exact) or default behavior.

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 verb (search), resource (video games on gg.deals), and intended outcome (find a game's ID). It distinguishes itself from siblings like get_game_prices or get_game_bundles, which serve different purposes.

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 explicitly says 'Use this to find a game's ID,' which clarifies when to use it. It doesn't state when not to use it, but the sibling names imply distinct use cases (prices, bundles, low).

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