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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds real behavioral context the annotations don't: the ranking criteria and the minimum 5-closed-trades filter that determines who appears. It stops short of noting result ordering stability, pagination, or what happens when a market has too few qualifying wallets.

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 dense sentence, front-loaded with what is returned and followed by the ranking and inclusion rules. Every clause earns its place and nothing is repeated from structured fields.

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 a full input schema and an output schema, the description only needs to explain the selection logic, which it does completely via ranking order and the trade-count threshold. Minor gaps remain around tie-breaking and empty-result behavior, but nothing essential to calling it correctly is missing.

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%, including market name formats, limit range, and window enum, so the schema carries the parameter burden. The description reinforces the meaning of 'market' via 'one Hyperliquid market' but adds no syntax or default detail beyond the schema.

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 resource (best traders on one Hyperliquid market) and the exact ranking rule (profit factor, then win rate) plus the inclusion threshold (5 closed trades). That combination separates it from generic siblings like get_top_traders or get_pnl_leaderboard, though it never names an alternative explicitly.

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: an agent can infer this is the tool for per-market trader ranking, but there is no statement of when to prefer it over get_market_top_wallets, get_top_traders, or get_pnl_leaderboard, and no explicit exclusions.

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