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

No annotations are provided, so the description carries the full disclosure burden; it does convey results are read-only rankings with wallet addresses and that ordering is by pnl or volume. However it omits freshness (daily/weekly snapshot vs live), what 'profit' means (realized vs unrealized), and any rate-limit or pagination notes.

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 front-loaded sentence that packs the resource, ranking dimensions, optional filter, and the useful payoff (wallet addresses) with zero filler.

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 read-only listing tool with an output schema and all parameters optional, the description covers what an agent needs to call it correctly. The main residual gap is data freshness and whether wallet addresses are always returned, which matters for downstream follow-up actions.

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 carry parameter meaning, and it does well: it enumerates valid periods (day/week/month/all-time), the two order_by modes (profit/volume), and category examples (politics, sports, crypto). Only 'limit' is left undocumented, though its default and type make it self-evident.

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 (Polymarket top traders) with concrete dimensions: ranking metric (profit vs volume), time window, and category. It is clearly not a markets or wallet-lookup tool, though it does not explicitly name the sibling tools (polymarket_wallet, polymarket_top_markets) whose domains it borders.

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 implied by 'top traders' — you call it when you want a ranked list of traders — but there is no explicit when/when-not guidance, no routing to polymarket_wallet for a specific address, and no guidance on choosing profit vs volume ranking.

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