get_top_traders

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that this is a read/list operation, but says nothing about data freshness, pagination, whether chain is required, or how the 'chain' value (typed as string|number) is interpreted.

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?

A single tight sentence with the resource and ranking dimensions front-loaded and no filler. It is efficient, though the brevity is part of why parameter and behavioral detail is missing.

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 no output schema, no annotations, and 0% parameter coverage, the description should explain the ranking inputs and the chain/period behavior, but it does not. An agent can form a rough call but cannot be confident about valid chain values or default period semantics.

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, yet it only gestures at the sortBy options ('P&L, win rate, volume, trade count') without naming the parameter. The chain, limit, and period parameters — including the period enum values and defaults — are entirely unaddressed.

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 gives a specific verb ('Get') and resource ('top performing trader wallets') plus the ranking dimensions, so an agent immediately knows what the tool returns. However, it does not distinguish itself from siblings like get_hl_top_traders or get_hl_top_traders_by_pnl, which look nearly identical in purpose.

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 guidance on when to choose this tool over the closely-named get_hl_top_traders or get_hl_top_traders_by_pnl siblings, nor any stated preconditions. The only implied usage is 'you want top traders', which is already obvious from the name.

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