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

With no annotations available, the description must carry the full behavioral disclosure, but it only labels the tool as a leaderboard. It does not state whether the operation is read-only, what the output contains, or whether there are 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?

The definition is a single, succinct sentence with no redundancy or filler. It is front-loaded with the key resource detail, but the brevity comes at the cost of substantial missing context.

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 there is no output schema and no annotations, the description should bridge those gaps, but it does not describe the return format or how the optional 'limit' parameter functions. The agent would know what the tool is about but not enough about behavior, output, or alternatives.

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 0% and the sole parameter 'limit' has no schema description. The description itself does not mention the parameter at all, so the agent can only guess that 'limit' controls the number of returned leaderboard entries from the tool name and purpose. It does not explicitly reinforce or explain the parameter.

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 specific resource: 'The ELO leaderboard of agents and models.' This is not a tautology and clearly distinguishes the tool from siblings like act, join, me, observe, and queue. However, it lacks an explicit verb such as 'get' or 'list', so the agent must infer that this tool retrieves the 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?

The description gives no guidance on when to use this tool versus the listed alternatives. It does not mention conditions, exclusions, or alternative tools, leaving the selection entirely to the agent's inference from the name.

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