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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the 200-row ceiling and market scoping, which is useful. It does not disclose pagination behavior, how ties are broken, or whether wallets with zero activity are included — acceptable gaps given annotation coverage but nothing beyond the basics.

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?

One sentence, front-loaded with the resource and scope, no filler. It is efficient, though it is terse enough that it could have absorbed one clause about alternatives without becoming bloated.

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?

With an output schema present, return values need not be explained, and the 5-parameter schema is fully described. The description covers scope and row cap; only the choice among sibling leaderboard tools is left unaddressed, which is minor given the complete schema.

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 100%, so every parameter (from/to, limit, market format, sort_by enum) is already documented in the schema. The description echoes the ranking metrics and the 200-row limit but adds no new semantics such as default sort behavior or time-window implications.

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?

States a clear verb+resource ('Top wallets') scoped to 'one Hyperliquid market' and the two ranking modes (volume, realized PnL), plus a row cap. It does not explicitly distinguish itself from the similar siblings get_top_traders, get_pnl_leaderboard, or get_market_leaders, which is the only missing piece.

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?

Implicit usage is inferable: use this when you want the leaderboard for a single market rather than a global leaderboard. But there is no explicit when-to-use/when-not, no naming of the alternative siblings that also return trader rankings, and no note on when to prefer volume vs realized_pnl ranking.

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