speedrun_get_game

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 implies a read operation but does not explicitly state if it is read-only, whether authentication is needed, or any rate limits. The description is minimal, leaving agents uncertain about constraints.

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 concise sentence of 10 words. It is efficient but lacks structure (e.g., bullet points). For a simple tool, this is acceptable, though slightly more detail could be added without increasing length.

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 no output schema, the description partially defines the output by mentioning 'categories and levels,' but misses other likely fields (e.g., description, release date). It does not differentiate from sibling tools like speedrun_search_games. Moderately complete for a simple retrieval tool.

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 100%, and the description adds only the phrase 'including categories and levels,' which hints at response content but does not add new meaning to the parameter beyond what the schema already provides. Baseline 3 is appropriate.

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 'Get details of a game on Speedrun.com including categories and levels.' It uses a specific verb and resource, and the purpose is distinct from sibling tools like speedrun_search_games or speedrun_get_leaderboard.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a game ID from a search tool, or when to prefer it over speedrun_search_games.

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