speedrun_get_leaderboard

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

No annotations are present, so the description must convey behavior. It only states 'Get' (implies read) but lacks details on error handling, pagination (e.g., top parameter defaults), rate limits, or response format. This is insufficient for a leaderboard tool.

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 short sentence, which is concise but at the expense of completeness. It earns its place but fails to include crucial details given the tool's 6 parameters.

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 tool with 6 parameters, no output schema, and no annotations, the description is incomplete. It omits explanations of optional parameters, result interpretation, and constraints (e.g., valid game/category IDs). Substantial gaps remain.

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 50% (half of parameters lack descriptions). The description adds no additional meaning to parameters like 'platform', 'emulators', or 'video_only', leaving them unexplained. The existing schema descriptions are minimal (e.g., 'Game ID').

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 retrieves the leaderboard for a Speedrun.com game category, using a specific verb and resource context. It distinguishes from sibling tools like speedrun_get_game (game details) and speedrun_list_runs (individual 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?

No guidance is provided on when to use this tool versus alternatives (e.g., speedrun_list_runs for filtering runs). No prerequisites or context are mentioned beyond the required parameters.

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