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

With no annotations, the description carries the transparency burden and does well: it discloses per-call cost, payment flow, authentication methods, the data source, insider/algo detection, and the educational/non-financial-advice caveat. It does not describe rate limits or exact return structure, but the core behavioral and access traits are covered.

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?

Purpose is front-loaded and the payment/auth instructions are actionable, but the description is heavier than necessary due to marketing language ('elsewhere this data class sits behind $599/mo API plans') and repeated auth alternatives. It earns its place mostly but could be tightened.

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?

Given three optional parameters, no output schema, and no annotations, the description provides enough context for an agent to understand what data is returned, how to pay, and how to authenticate. The main gaps are the unexplained min_bets parameter and the absence of explicit sort_by value constraints.

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. It partially does by naming likely sort_by values (informed score, win rate, realized PnL, volume) and implying limit through 'leaderboard'. However, min_bets is not explained at all, and no explicit accepted values are given for sort_by.

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 clearly identifies the tool as a Polymarket smart-money leaderboard and specifies the ranking dimensions (informed score, win rate, realized PnL, volume) plus extra data like specialization and average entry odds. It does not explicitly differentiate itself from the similarly named sibling get_polymarket_whales, so it falls just short of a 5.

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?

The intended use is implied by the description (retrieve a whale leaderboard with ranking metrics), and it provides practical caller guidance about x402 payment and subscriber API keys. However, it does not state when to choose this tool over alternatives like get_polymarket_whales or get_polymarket_new_wallets.

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