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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description does add genuinely useful behavior beyond that – it discloses the tool is paid (x402, ERC-8183 escrow) with specific prices – but the price statement is internally inconsistent ('0.10 USD1, or half that in $BOBAI' vs '0.10 $U'), and it never clarifies whether the returned payload is the answer or just terms.

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?

A single run-on block that repeats the payment arrangement twice with conflicting figures and spends most of its length on sales framing rather than the tool's behavior. The one decisive concept, break-even spacing, is buried mid-sentence.

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 must carry the return-value burden, and it partially does by naming the computed fields (grid levels, swap fee, price impact, transfer tax, break-even spacing). However it leaves the critical ambiguity of what the caller actually receives versus what must be purchased unresolved, which matters for a paid tool.

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% (the single 'task' parameter is documented as 'What you want, with the address in it'), so the baseline is 3. The description adds no extra meaning, format, or examples for the task string.

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 middle of the text does state a concrete deliverable – grid levels for a BNB Chain pool plus round-trip cycle cost (swap fee, price impact, transfer tax) and break-even spacing – so it is more than a tautology. But it is wrapped in pricing/marketing phrasing and never resolves whether the call returns the plan itself or merely 'the terms,' nor distinguishes it from sibling bsc_pool_scan.

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 when-to-use guidance: nothing says when this beats bsc_pool_scan, what inputs are needed beyond 'the address,' or what prerequisites exist. The only routing information concerns payment channels, not tool selection.

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