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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering safety. The description adds 'opaque cursor pagination' as a behavioral trait, which is useful. However, it does not disclose rate limits, default sorting behavior, or the interplay between offset and cursor. Minimal extra value beyond annotations.

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 with no fluff. The main action and key data are stated immediately, and the pagination detail is appended efficiently. Appropriate length for the information provided.

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 8 parameters and an opaque pagination mechanism, the description is too terse. It does not mention filter options (category, timePeriod, userName) or the dual pagination (offset vs cursor). While an output schema exists and annotations cover safety, an agent still lacks guidance on parameter selection and pagination usage, making this incomplete for a tool of this complexity.

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 only 13% (only cursor has a description). The description mentions 'opaque cursor pagination' providing context for the cursor parameter, and 'volume in shares and PnL in USD' hinting at orderBy values, but it does not explain limit, offset, category, timePeriod, userName, walletAddress, or the relationship between offset and cursor. For 8 parameters, the description fails to compensate for the low schema coverage.

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 ('Get') and resource ('ranked public Polymarket traders') with key output attributes (volume in shares, PnL in USD). This clearly distinguishes it from market, position, and wallet tools. Although there is a sibling named 'get_trader_leaderboard' that may be identical, the description itself is unambiguous about the tool's function.

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?

No usage guidance is provided. The description does not mention when to use this tool over alternatives, nor does it reference any sibling tools or conditions. An agent would have to infer applicability from the purpose alone, which is insufficient given the large number of related get_* tools.

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