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

No annotations are provided, so the description carries the burden. It discloses the tool returns a Level-2 order book with specific fields and hints at the analytical value (spotting bad fills). It does not disclose whether this is a read-only operation, rate limits, or what happens for illiquid/nonexistent markets, but the read-only nature is strongly implied by 'order book' context.

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 reasonably concise and front-loaded with the core purpose. The final sentence about equities/indices/commodities is useful but slightly tangential. Overall it earns its place without excessive verbosity.

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?

The description explains what the tool returns and why it matters, which is good for a market data tool. However, with no output schema and vague parameter semantics, an agent lacks critical details about how to specify the market (symbol vs id vs instrument) and what the exact response shape is. The complexity is moderate, so this is a noticeable but not fatal gap.

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% but the parameter descriptions are generic placeholders ('Id to process', 'Depth to process', 'Symbol to process', 'Instrument to process') that add no real meaning. The description doesn't clarify which parameter identifies the market, how depth is expressed, or the relationship between symbol and instrument. With 4 parameters and no required ones, an agent cannot confidently know what to pass.

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 clearly states it is a Level-2 order book for one Polymarket Perps market, listing the specific microstructure fields (best bid/ask, spread, midpoint, cumulative depth, imbalance). It distinguishes itself from generic market data tools by emphasizing the pre-trade microstructure focus, though it doesn't explicitly name a sibling alternative.

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?

The description implies usage context: before sending an order, to spot bad fills via thin books and lopsided depth. It also notes it works on equities, indices, and commodities as well as crypto, which broadens applicability. However, it doesn't explicitly state when NOT to use it or name alternative tools like x402-polyperp-quotes or x402-polyperp-exchange.

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