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

With no annotations, the description must carry the behavioral disclosure burden. It does state the authorization requirement (Bearer token), which is a useful prerequisite. However, it does not disclose that this is a read-only operation, what the response contains, or any pagination or default behavior, making it only minimally transparent.

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 very short, which is positive, but the brevity contributes to under-specification rather than efficient coverage of necessary information. The auth requirement is placed after the main noun phrase, and all critical parameter context is omitted, so it is not a well-structured minimum viable description.

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 the tool's simplicity (two optional parameters, no output schema), the description should at least explain what the leaderboard returns and how ranking values (eth_earned vs signal) affect ordering. It does neither, so an agent cannot fully predict the tool's behavior without external knowledge.

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 description coverage is 0%, so the description must compensate for the lack of parameter documentation, but it mentions neither 'limit' nor 'ranking'. The agent is left with only type/enum information from the schema and no explanation of what these parameters control or how they affect results.

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, 'Agent Arena leaderboard', which clearly indicates the tool retrieves a ranked list of agents. The plural 'agents' in the tool name and the word 'leaderboard' differentiate it from sibling get_agent. However, it is a noun phrase rather than an explicit verb statement like 'Get the Agent Arena leaderboard', so it falls just short of a perfect 5.

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?

There is no guidance about when to use this tool versus alternatives such as get_agent or get_signals. The description does not provide any context for typical use cases, scenarios, or exclusions, leaving the agent to infer appropriateness 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.