get_top_traders

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

No annotations provided, and description only states the core functionality without disclosing behavioral traits like pagination limits, data freshness, or rate limits. For a read-only aggregation tool, minimal transparency beyond schema is offered.

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?

Single sentence, front-loaded with verb and resource, no extraneous information. Efficiently conveys the tool's purpose.

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 simple list tool with only three optional parameters and no output schema, the description covers the main functionality. It could mention return format or query source, but overall is complete for the scope.

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?

Input schema covers all three parameters with descriptions, and the description mentions ranking metrics aligning with the orderBy enum. However, description adds no new meaning beyond schema; baseline 3 appropriate due to high 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?

Description clearly states the tool retrieves top Polymarket traders ranked by specific metrics like realized P&L, win rate, or volume. It specifies the source (Beefy P&L subgraph) and differentiates from sibling tools focused on individual account data or market details.

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?

Description does not provide explicit guidance on when to use this tool versus alternatives such as get_trader_profile or get_account_pnl. Usage is implied but not explicitly contrasted with siblings, leaving the agent to infer context.

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