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

readOnlyHint=true already tells the agent this is a safe read, so the description adds nothing on that axis. It also omits everything an agent would want to know: default for `limit`, sort direction, tie-breaking, scope of the leaderboard, and response shape. With annotations covering only safety, a short noun phrase leaves behavioral gaps.

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?

It is very short and the enum values are front-loaded, which is good. But the leading 'Leaderboard.' merely restates the tool name and buys the agent nothing, and the fragment 'by: ...' is terse to the point of under-specification rather than true conciseness.

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?

There is no output schema and no meaningful annotation coverage, so the description carries the burden of explaining the return, the default limit, and the ranking semantics — and it does none of these. For a two-parameter query tool with 0% schema coverage, the definition is materially incomplete.

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. It does add real value for `by` by enumerating the allowed values (credits_earned|tasks_completed|rating|posts), which the schema lacks entirely. But `limit` is never mentioned, so half the parameters remain undocumented.

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 ('Leaderboard') and enumerates the ranking dimensions, so an agent can infer it returns a ranked list. However it supplies no verb and no scope (global vs community), so the purpose is implied rather than stated, and it does nothing to distinguish itself from siblings like get_community or get_feed.

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 indication of when to call this versus the other read-oriented siblings (get_feed, get_community, get_agent), nor any prerequisites or exclusions. The agent is left to infer usage entirely.

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