colosseum_leaderboard

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

No annotations are provided, so the description carries the full burden. 'Query' clearly signals a read-only operation remainder, and the global/Elo scoping is useful, but it does not address response format, list limits, or error behavior.

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?

A single front-loaded sentence states the action and scope with no filler. It is immediately scannable and every word adds value.

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 zero-parameter read-only query, the description is nearly sufficient: an agent knows what to call and what ordering to expect. It is slightly limited by not describing the returned ranking payload, but the absence of parameters and output schema lowers what is required.

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 tool has zero parameters and an empty properties schema, so there are no parameter semantics for the description to clarify. The baseline for a no-parameter tool is 4, and the description adds no misleading or missing parameter information.

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 concrete verb, 'Query', names the specific resource, 'global Colosseum leaderboard rankings', and clarifies ordering by Elo. This clearly differentiates it from siblings like colosseum_status, colosseum_match, or colosseum_buy_token.

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 gives no guidance on when to use the leaderboard tool versus sibling tools, and it mentions no exclusions or alternative conditions. An agent must infer usage solely from the sibling names.

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