speedrun_list_runs

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

No annotations provided, and description only states 'list speedruns'. Fails to disclose read-only nature, rate limits, authentication requirements, or pagination behavior, leaving the agent uncertain about side effects.

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?

Single sentence of 10 words, front-loads the action 'list speedruns' and optional filters. No fluff or redundancy.

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 7 parameters, no output schema, and no annotations, the description is insufficient. Omits pagination, sorting, result format, and does not specify that only the displayed filters are available. Leaves the agent with many gaps.

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 71% (5/7 parameters described); description merely restates some filterable fields (game, category, user, status) without adding meaning beyond schema. Does not explain 'max', 'orderby', or 'direction' parameters.

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?

Description clearly states it lists speedruns with optional filters for specific fields (game, category, user, status). This distinguishes it from sibling tools like speedrun_get_game or speedrun_search_games, which focus on single resources or broader search.

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 (e.g., speedrun_get_leaderboard). Does not mention prerequisites, context for filtering, or 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.