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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful non-annotation context — the $0.03 USDC per-call cost on Base — but says nothing about pagination, result limits, or rate/throughput behavior.

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 short and front-loads the purpose, but the pricing sentence is duplicated almost verbatim ('$0.03 USDC x402 Base.' then '[x402: 0.03 USDC per call on Base]'), wasting one of only two sentences on redundancy.

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 tool whose only input is an unspecified free-form string and which has no output schema, the description omits the input format, the output shape, and how the advertised filters and per-wallet aggregation are actually requested. An agent would have to guess how to construct a call.

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 one free-form string parameter named 'input', and its schema description is a verbatim copy of the tool description, so it conveys no expected format, syntax, or examples. Even at 100% nominal coverage the parameter text adds no meaning, and the description does not compensate for this ambiguity.

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 ('Historical Polymarket trade query') plus scope ('filters plus per-wallet aggregation'), which is enough to separate it from the sibling polymarket_markets. It stops short of an explicit contrast with that sibling, so it is clear but not fully differentiating.

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?

There is no statement of when to use this tool versus polymarket_markets or any other sibling, no prerequisites, and no mention of when not to use it. 'With filters' hints at capability but never names the filters or the conditions that call for them.

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