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

Annotations only declare the read-only, idempotent, non-destructive profile; the description adds substantive behavior: cap of 50 with default 20, sort semantics, exclusion of sub-$1 and resolved positions (with a note in the text), and inclusion of totals and portfolio value. That is well beyond annotation coverage.

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 usage trigger is front-loaded and the sentences are dense with concrete facts. The return-value sentence is long and enumerates fields already covered by the output schema, which is mild redundancy, but nothing is filler.

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 three-parameter read tool, the description covers triggering, input forms, result shape, size limits, sorting, and exclusions. An agent can call it correctly without inspecting the schema or output schema.

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 the baseline is 3, but the description adds value by enumerating the accepted trader identifier forms (0x address, profile URL, @username, username) and by tying natural-language intents like 'biggest position' and 'up the most' to the sort options. It still doesn't add formatting rules or edge-case handling beyond 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?

States a specific verb and resource ('a Polymarket trader's open positions or holdings') and backs it with concrete user-style queries. It is clearly distinct from siblings like get_trader_profile (identity/aggregate) and get_whale_trades (market-wide activity).

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?

Provides strong when-to-use signal via four representative example questions, including 'biggest position' and 'up the most'. It does not name a sibling alternative or state when not to use it (e.g., profile/summary requests should use get_trader_profile), so it falls short of the top mark.

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