Top traders leaderboard

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

The annotations already disclose that this is a read-only, open-world data tool. The description adds useful context about bot and one-off-wallet filtering plus a follow-up workflow, but it does not explain data freshness, ranking methodology details, or response shape beyond the schema parameters.

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 description is three sentences, front-loads the core action, then provides concrete use cases and a sibling-tool pairing. No sentence is redundant, and the progression is easy for an agent to scan.

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 nine-parameter read-only leaderboard with no output schema, the description adequately covers purpose, usage, filters, and follow-up workflow. It could go further by describing the response fields or paging model, but the full schema already carries the parameter detail.

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 all nine parameters are already well documented. The description reinforces the main ranking dimensions, periods, and filters, but adds little syntax or semantics beyond what the schema provides; baseline 3 applies.

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 states a specific verb and resource: rank Hyperliquid traders by realized profit, win rate, or volume over selectable periods. It also distinguishes this leaderboard tool from sibling wallet-inspection tools by naming hydromancer_wallet_overview as the follow-up for holdings.

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?

It gives clear example use cases (“best traders this week”, “consistent winners on stocks”, “top traders using builder X”) and explicitly pairs the tool with hydromancer_wallet_overview. It does not spell out when not to use it or name a competing ranking alternative, but the intended context is clear.

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