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

Annotations already declare read-only, open-world, and non-destructive behavior, but the description adds substantial context beyond them: x402 payment terms, holder-pass signature-only access, what the returned cost represents, and the concentration of fees. It also explicitly says calling the tool returns terms rather than executing swaps, which is useful behavioral disclosure.

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 a dense, run-on block mixing purpose, payment mechanics, return values, and caveats. The core purpose is front-loaded, but excessive parenthetical detail and sales-channel information obscure the actionable parts.

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 complex paid planning/range-checking tool with no output schema, the description provides some return-value context (cost share, named holding, range details) and payment mechanics. However, it remains unclear how to structure the free-form task input and what exactly is returned before versus after payment.

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?

There is one parameter with 100% schema description coverage, so the schema already documents it. The description does not add syntax, examples, or constraints for the free-form task parameter beyond the schema's 'What you want, with the address in it.'

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 names several related operations — portfolio rebalance costing, swap planning, and liquidity range checking — but never states cleanly whether the tool plans, quotes, or executes. It also does not differentiate itself from the sibling tool pancakeswap_best_route. The core purpose is inferable, but the payment/x402 framing makes it ambiguous.

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?

It describes scenarios ('For liquidity it rebalances ranges') but gives no explicit when-to-use guidance, no exclusions, and no comparison to the sibling tool. An agent must infer the conditions for choosing this tool.

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