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

With no annotations, the description carries the full burden, and it discloses two important traits beyond the schema: that the data is unvetted/spam-prone, and that the call costs $0.01 USDC on Base via x402 — a payment gate the agent would otherwise miss. It also explains the return content, including first-seen risk scores and venue-level 24h liquidity-loss history, though it says nothing about rate limits or whether the risk score is computed at first sight only.

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 lead sentence front-loads chain, window and venues, and the two-sentence span is efficient given how many return fields must be described. The field enumeration is dense and reads as a run-on list, but each item conveys distinct return content rather than filler.

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, the description does the job of describing return fields, including quote liquidity caveats ('where readable'), and it flags the spam risk and payment cost. Coverage is strong for a two-parameter listing tool; only rate limits and the risk-score methodology are left unstated.

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%, and both parameters carry ranges and defaults, so the schema already does the work; the description only references the 'last N minutes' window implicitly. The one nuance it adds is the 'newest first' ordering implied by the schema, but the schema's Arbitrum block-cap note is not reconciled with this Optimism tool, leaving 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?

The description gives a specific verb and resource ('New trading pools created on OP Mainnet in the last N minutes') and narrows it to named venues (Uniswap v4/v2/v3, Velodrome), which separates it from the sibling chain variants such as eth_new_pools, base_new_pools and polygon_new_pools. It also enumerates the returned fields, so an agent knows exactly what discovery surface it gets.

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 implied by the chain and venue scoping and by the 'Unvetted: many new pools are spam' caveat, but the description never states when to prefer this over optimism_token_snapshot, token_risk_check, optimism_large_trades or the other chains' new-pools tools. There are no explicit exclusions or prerequisites beyond the cost note.

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