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

No annotations are provided, so the description carries the full burden. It does disclose what the tool returns (the computed trend statistics) and how candles behave (intervals, 24/7 coverage), which is genuinely useful, but says nothing about pagination, result limits, or the x402 payment/auth requirement implied by the tool family.

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?

Front-loads the resource, then the returned statistics, allowed intervals, usage hint, and a caveat. Dense but largely earned; the heavy 24/7/equities sentence is the only arguably expendable part.

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 no output schema, no annotations, and 6 undocumented parameters, the description does good work on return contents and interval behavior but leaves the identity/selector parameters unresolved. An agent would know what it gets back yet still be unsure how to target the right market.

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 0% across 6 parameters, and the description only defines the valid values for 'interval' (1m through 1w). The overlapping identity parameters id/symbol/instrument are never disambiguated, and hours/limit are left entirely undefined, so the description fails to compensate for the coverage gap where it matters most.

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: OHLCV candles for a single Polymarket Perps market, and enumerates the derived statistics (first open, last close, percent change, high, low, avg volume, total trades, direction). This clearly separates it from siblings like x402-polyperp-trades or x402-polyperp-book, though it does not name any sibling explicitly.

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 an intended-use hint ('momentum, breakout and mean-reversion checks') and a useful context note about 24/7 trading, but never states when NOT to use it or which sibling (e.g. trades, book, quotes) covers an adjacent need. Usage is implied rather than routed.

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