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

Annotations already declare readOnlyHint=true, idempotentHint=true, non-destructive, and closed-world, so the safety profile is fully covered. The description adds only the statistical window concept and the entity-per-row grain; it says nothing about the anonymous-vs-signed-in allowance asymmetry already present in the schema, so it clears the lowered bar without excelling.

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?

Two compact sentences, zero filler, with the core operation (ranking) front-loaded and the grain clarification trailing. Nothing can be cut without losing information.

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 an 18-parameter, no-required-args tool with no output schema, the description covers the core semantics but says little about the return shape beyond row grain or about default behavior (default sort, anonymous sample size, offset restrictions). The schema carries most of that, but a ranking tool with this many knobs warrants a bit more orientation.

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 83%, so the schema already documents the meaningful parameters (sort default, limit cap, minRoi scale, period values, bands). The description adds no param-level meaning beyond the generic 'with filters', which is the correct baseline when the schema does the heavy lifting.

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 verb+resource: ranking Polymarket traders by realized PnL and other stats over a configurable window with filters. It also clarifies the row grain ('one trader, possibly several wallets'), which implicitly separates it from the single-entity `entity` sibling. It stops short of naming an alternative tool the way a 5 would.

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 reach for leaderboard versus entity, account, or fills, and no mention of prerequisites such as sign-in level. 'With filters' is an implied usage, but nothing routes the agent between competing tools.

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