polymarket_whale_positions

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

No annotations are provided, so the description must disclose behavioral traits. It only states that the tool returns whale positions, but does not mention rate limits, data freshness, authentication needs, or whether it is read-only. Essential behavioral context is missing.

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 very concise, consisting of two short sentences. It is front-loaded and every phrase adds value. The 'Copy-trade reference' might be integrated, but overall it is efficient.

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?

Lacks important information such as output structure (fields returned), number of results, pagination, or error handling. For a tool with no output schema, the description should help the agent understand what data to expect, but it only mentions 'wallets and positions' without detail.

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?

The single parameter 'min_position_usd' is explained by the description mentioning 'sized >$10k' which aligns with the default. The schema has no property descriptions, but the tool description adds meaningful context for the parameter, though it could specify constraints like positive values.

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 top Polymarket whale wallets with positions >$10k, with a copy-trade reference. It is specific about the resource and its scope, and distinct from sibling tools which cover different topics.

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 explicit guidance on when to use this tool vs alternatives. The description mentions 'copy-trade reference' implying a use case, but does not specify conditions or alternatives. Differentiation from siblings is implicit via domain but not stated.

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