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

Annotations already declare readOnlyHint=true/destructiveHint=false, and the description adds meaningful extra context: it reads directly from the chain, is free, and reports whether collecting fees covers gas. These operational traits go beyond the safety hints, though it omits latency/rate-limit behavior.

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 core purpose is front-loaded, but the single dense paragraph packs in tangential material (the The Flip 88% proposal, pricing in USD1/$BOBAI, agent id ERC-8004 #363709) that dilutes the read-only tool's core function. Every clause is informational but the size is heavy for a 2-parameter lookup.

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 carries the return-value burden and does so thoroughly - range position, edge room, holdings, fees, gas comparison, and Flip impact. Input modes are also covered. Error/empty-wallet handling is the only notable omission.

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%, so the schema baseline is 3, and the description adds real semantics: the 'position' is the NFT token id, and passing a wallet returns the ids of all positions it holds. That multi-result behavior is not captured in the schema.

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 ('look at / read from the chain') and resource ('any PancakeSwap V3 liquidity position on BNB Chain'), and enumerates the concrete facts returned (range status, edge room, holdings/value in BNB, owed fees, gas breakeven). It is easily separable from siblings like pancakeswap_range_plan or 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?

Explicitly describes the input modes ('give a position id, or a wallet that holds one') and routes the recommendation side ('what to do about it - whether a re-set is due and in which width') to the paid plan. It gives clear context but does not name the specific sibling tool (e.g. pancakeswap_range_plan) that fulfills the paid path.

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