Polyrank highest-ROI resolved trades

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds context that only resolved, won positions are included, with a real cost floor, and identities are masked. This provides useful behavioral detail beyond what annotations offer, with no contradiction.

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?

The description is two sentences, front-loaded with the core purpose and key details. Every sentence adds value without unnecessary words.

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 5 parameters, 2 enums, and no output schema, the description covers the core concept and one optional filter but omits return format details, explanation of sort keys, and limit behavior. It is adequate but not fully comprehensive.

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 coverage is 100%, so baseline is 3. The description mentions the category filter but does not add extra meaning for parameters like sort, dir, limit, or since_days. It provides minimal additional value over the schema.

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 states the tool returns the biggest return-on-cost resolved Polymarket bets (won positions with a real cost floor), acting as a hall-of-fame of single trades by ROI multiple. This specific verb+resource combination distinguishes it from siblings like leaderboard or pulse.

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 description mentions optional category filtering and identity masking but does not explicitly state when to use this tool versus alternatives like polyrank_get_leaderboard or polyrank_get_trader_skill. Usage context is implied but not elaborated.

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