speedrun_search_games

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

No annotations are provided, so the description must disclose behavioral traits. It only states that no API key is required, but does not mention any other behaviors such as rate limits, default max value, return format, or error handling. This is insufficient for a tool with no annotation support.

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 of 10 words, efficiently communicating the tool's purpose and a key trait (no API key). It is appropriately front-loaded with the action. Every word earns its place.

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?

For a simple search tool with two parameters and no output schema, the description covers the core purpose and a major usage constraint (no API key). However, it omits information about default max value, whether results are paginated, and what the response looks like. While the tool is simple, these details would improve completeness.

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 has descriptions for both parameters (100% coverage). The tool description adds only the phrase 'by name', which reinforces the 'name' parameter but does not add new semantic information. For the 'max' parameter, no additional context like default or range is provided. So the description adds minimal value over the schema.

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 uses a specific verb 'Search' and resource 'games on Speedrun.com', and specifies the search criterion 'by name'. This clearly differentiates from sibling tools like speedrun_get_game (which retrieves a specific game) and speedrun_list_runs (which lists runs).

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 mentions 'No API key required', which is a useful note for selecting this tool over others that might require authentication. However, it does not explicitly state when to use this tool versus alternatives like speedrun_get_game or speedrun_get_user, missing guidance on when not to use it.

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