Season 0 leaderboard

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the scoring model (2 points per predicted match, 15 per streamed match), which is real behavioral context, but says nothing about whether the call is read-only, side-effect free, or what the standings contain.

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 compact sentence with no waste. It is front-loaded with the resource, though the sentence spends most of its length on scoring rules rather than the tool's action.

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?

With no output schema and no annotations, the description should describe the shape of the standings it returns (rank, user, points) or confirm read-only behavior. It explains how points are earned but not what comes back, leaving a real gap for a zero-param 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?

The tool takes zero parameters, so there is no parameter semantics to document; baseline 4 applies. The description adds no parameter confusion either.

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 names the resource (Season 0 standings/leaderboard) but is a noun phrase with no retrieval verb, so the action is only implied. It does not reference any sibling, though none of icare_bet/icare_positions/icare_wallet is obviously a leaderboard, so confusion risk is low.

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 statement of when to call this versus the other icare_* tools, and no prerequisites or exclusions. The agent must infer that this is a read-only standings lookup from the name alone.

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