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

No annotations are provided, so the description carries the entire burden, and it discloses nothing: not whether results are paginated or limited by default, how ties are broken, whether the ranking is cached/periodic, or what happens when metric=pr/wtr is combined with a non-lifetime period (a nuance buried only in the schema).

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 two-word description is technically compact but represents under-specification, not conciseness. Nothing is front-loaded because nothing informative is present.

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 9-parameter, unannotated, no-output-schema leaderboard tool with 44% parameter coverage, the description supplies none of the context an agent would need — return shape, default limit, or how the metric/period interaction works. It is wholly inadequate for the tool's complexity.

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 only 44% across 9 parameters, and five of them (lang, strict, language, min_tier, languages) have no description anywhere. The tool description adds zero meaning beyond the schema, so parameters like strict, min_tier, and the lang/language/languages redundancy are left entirely unexplained.

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?

"Top players" merely restates the tool name and adds no verb or scope. It does not distinguish this leaderboard from siblings such as clans_top, clans_stronghold_top, or players_onslaught, nor does it say what a "top player" entry contains or how ranking is ordered.

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 when-to-use guidance, no mention of alternatives, and no prerequisites. The agent must infer from the schema enums alone that this is a leaderboard query rather than a player lookup (players_by_nickname) or comparison (players_compare).

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