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

With zero annotations the description carries the full burden and does well: it discloses the paid access model ('Costs $0.01 USDC on Base via x402'), flags the data as unvetted/spam-prone, and hedges output coverage with 'quote liquidity where readable'. It stops short of describing failure modes or what happens if payment is unavailable.

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?

Highly front-loaded: chain, scope, venues and output fields come first, then the spam caveat and the price. The opening sentence is long and list-heavy, but every clause carries information an agent needs.

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 two-optional-param, annotation-free tool with no output schema, the description covers inputs, return shape, data quality risk and the x402 payment requirement. The remaining gap is operational: it doesn't say what the agent must have pre-arranged to satisfy the $0.01 USDC charge.

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 description coverage is 100% and both parameters (limit, minutes) are fully documented with ranges and defaults in the schema. The description only echoes 'last N minutes' without adding format or interaction details, so the baseline 3 applies.

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 resource and scope: new trading pools on Polygon PoS created in the last N minutes, restricted to Uniswap v4 and v3. It also enumerates the returned fields (token symbol/name/decimals, fee tier, v4 hooks, POL/WPOL/USDC pairing, quote liquidity), which clearly separates it from polygon_token_snapshot, polygon_large_trades and the *_new_pools siblings on other chains.

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 described output (fresh pool discovery) and the warning that 'many new pools are spam' sets expectations, but no alternative is named (e.g. polygon_token_snapshot or token_risk_check for vetting) and no explicit when-to-use/when-not condition is given.

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