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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a real behavioral rule beyond structured data: wallets with fewer than 5 fills in the window are excluded, which materially affects interpretation of results and is not in the schema. It does not mention pagination/truncation behavior beyond the schema's limit.

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 sentences, no filler, with the core purpose front-loaded and the eligibility caveat as a follow-up. Every clause carries 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?

An output schema exists and annotations cover safety, so the description needn't explain returns. Given four optional params with full schema documentation, it is essentially complete; the only missing piece is routing guidance versus the sibling ranking tools.

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% with formats, defaults, and the sort_by enum fully documented, so the baseline applies. The description's 'over a window' and metric list only mirror from/to and sort_by without adding syntax or edge-case meaning.

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 specific verb (ranked), resource (every Hyperliquid wallet), and the metrics used (realized PnL, losses, volume) over a window — an agent knows exactly what comes back. It does not differentiate itself from plausible siblings like get_top_traders, get_market_top_wallets, or get_vault_leaderboard, which also return ranked wallets.

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?

Usage is only implied by 'ranked ... over a window'; there is no statement of when to pick this over the other leaderboard/ranking siblings, nor any prerequisite or exclusion guidance. An agent must infer the choice from sibling names alone.

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