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

With readOnlyHint=true and destructiveHint=false annotations present, the bar is lower, yet the description still adds substantial behavioral context: it explains that quoted prices come from the venue itself, that the transfer tax is applied between legs because it is taken outside the pool where quoters cannot see it, and that the tool cannot detect an owner who has not acted yet. These are genuine disclosures beyond the annotations, with no contradiction.

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 well-organized with FIRST/SECOND structure and front-loads the core purpose, but it is long and occasionally stylistic ('where no quoter can see it', 'and it says so') where plainer wording would do. Every sentence carries some information, yet the prose is denser than necessary for an AI agent to parse efficiently.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does: best route, cost of every other route, round-trip with and without tax, and required slippage. It also covers the tool's limitations and the two questions it answers, leaving an agent with a complete picture despite medium-high complexity and no structured output metadata.

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%, so the baseline of 3 applies. The description reinforces the meaning of 'usd' by referencing 'this size' and slippage at size, but it adds no parameter-specific syntax or format details beyond what the schema already documents. It is adequate, not additive.

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 states a specific verb and resource: it determines the best route for a PancakeSwap swap, selecting among up to five pools by actual quoted return at the given size rather than by depth. It also distinguishes itself from nearby siblings like pancakeswap_fee_tiers, pancakeswap_range_plan, and bsc_pool_scan by framing itself as the pre-signing route/slippage decision tool for a swap.

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?

The opening clause 'For an agent about to swap on PancakeSwap' gives a clear trigger condition, and the closing warning 'It is not a safety certificate' tells the agent when not to rely on it. It does not name specific sibling alternatives to use instead, but the context is strong enough that the intended placement is unambiguous.

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