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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is lower, and the description still adds material context the annotations cannot: the call is metered and requires x402 payment or a paid key, and the record is keyed to a wallet rather than a person. It omits rate limits, error behavior, and whether P&L figures can be stale, but the paid-access disclosure is a genuinely important operational trait.

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?

Very short and front-loaded with the resource and its return contents. The telegraphic, fragment-style phrasing ('won X of Y with the sample size') and the inline x402 URL are slightly noisy, but no sentence is redundant.

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?

With one parameter, no output schema, and full annotation coverage, the description does the work an output schema would normally do by listing the record's fields and their provenance labels. Payment requirement and the wallet-vs-person caveat are both stated, leaving only minor gaps around freshness and failure modes.

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?

There is a single parameter with 100% schema description coverage ('Polygon wallet, 0x + 40 hex'), so the schema already carries the syntax. The description reinforces that the address is a Polygon wallet and adds the conceptual caveat that the record belongs to a wallet, not a person, but contributes no format or validation detail 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?

The description names the resource precisely ('A Polygon (Polymarket) wallet's record') and enumerates the contents returned (win rate with sample size, P&L with audit labelling, category split, tag), so an agent knows exactly what it gets back. It is phrased as a noun phrase rather than a verb+resource statement and never names a sibling, so differentiation from pm_smart_money_entries or pm_edges is left to inference.

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?

Usage is only implied: fetch a wallet's track record by address. The description does disclose a hard prerequisite ('Paid only ... x402 ... or a paid key'), which is more than nothing, but it gives no when-to-use versus the sibling board/edge tools and no explicit exclusions.

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