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

Goes far beyond the readOnly/destructive annotations by explaining data freshness ('pool figures are never cached, contract properties for up to 6 h'), error semantics ('quotable: false with a reason is an answer, not an error'), and measurement methodology ('transfer tax MEASURED from executed trades'). This gives an agent crucial expectations that annotations alone do not.

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 dense and long, but the core purpose is front-loaded and nearly every subsequent sentence adds a distinct behavioral caveat or return detail. It could be better structured with bullets, but it earns its length given the tool's complexity and lack of an output schema.

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 full burden of describing return values, and it does so comprehensively: cost per trade size, 1% price-impact USD size, measured tax, LP state, sellability, venues, and GoPlus contract properties. It even covers null handling and cache semantics, leaving little an agent would need to infer.

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?

The schema already fully documents the address parameter, covering token addresses, pool/pair addresses, and links. The description adds meaning beyond that by stressing 'ANY token or pool' and noting that a four.meme token without a pool is still handled, which meaningfully clarifies accepted input behavior for the single parameter.

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?

Opens with a specific verb and resource: 'Measure what a trade on BNB Smart Chain would actually cost, for ANY token or pool — before placing it.' It also distinguishes itself from router slippage figures ('not the headline slippage a router shows'), which separates it from sibling tools like pancakeswap_best_route.

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 frames when to use it ('before placing' a trade) and covers a special case ('A token still raising on four.meme with no pool yet is measured from four.meme's own contract instead'). It does not explicitly name when-not-to-use alternatives, but the context is clear enough for an agent to choose this tool for cost measurement.

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