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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: 'Public on-chain data only', which signals no authentication or private data is involved, and it enumerates what data is returned.

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?

Usage guidance is front-loaded and every sentence carries information — intent triggers, accepted inputs, returned fields, and data source. It is a dense single paragraph rather than over-long, though splitting the return contents into a list would improve scannability.

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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: track record metrics, open positions with entry/current price and unrealized P&L, event-grouped exposure, unredeemed settled winnings, and recent trades. An agent knows both what to pass and what it will get back.

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 100% and the single parameter already documents all three accepted forms (0x address, profile link, username). The description restates those accepted input forms, reinforcing but not extending the schema, so the baseline of 3 applies.

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 (retrieve a wallet's holdings and track record) and frames it around concrete user intents — 'what a Polymarket trader or wallet holds, how good a trader is'. It also anchors itself against the sibling pm_flow by mentioning wallets seen there, so it is distinguishable from pm_book, pm_leaderboard, etc.

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?

Gives explicit trigger conditions (user asks about holdings, trader quality, or sizing up a wallet from pm_flow). It does not state when not to use it or name a concrete alternative tool for overlapping needs, so it stops short of a 5.

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