get_leaderboard

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

Discloses returned fields (username, display name, token balance, mining power, rank) but does not mention ordering direction, potential pagination, or rate limits. Since no annotations exist, more detail would be beneficial.

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?

Two concise sentences, front-loaded with purpose and followed by output details and authentication note. No extraneous information.

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?

Lists output fields and specifies limit defaults, which compensates for lack of output schema. Missing explicit statement that results are sorted descending by token balance, but rank implies ordering. Adequate for a simple read 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?

Schema coverage is 100% for the single parameter, and the description repeats the default and max values already present in the schema. No additional semantic value added beyond what the schema provides.

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?

Clearly states the tool gets the top 50 leaderboard of Toleno users ranked by token balance, specifying the resource and verb. Unambiguous and distinct from sibling tools like get_global_stats or get_profile.

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?

States it is a public endpoint requiring no API key, which is useful. However, no guidance on when to use this tool versus alternatives like get_global_stats or when not to use it.

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