rebalancer

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

readOnlyHint=true already tells the agent nothing is executed, so the bar is lower. The description usefully adds that the output is a cost quote that scales with trade size ('at your size'), but it never explains the paid-half mechanics, whether any payment/auth is needed for that half, or the shape of the returned route/cost data.

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?

Only two sentences, so it is not bloated, but it front-loads a marketing frame ('Portfolio rebalancing, the free half') instead of the action. The free/paid metaphor consumes roughly half the text without conveying callable information.

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 return-value meaning, and it only partially does ('which pool' and 'what it costs'). For a simple 2-parameter quoting tool this is minimally adequate, but the route/cost payload and the relationship to the paid sibling remain underspecified.

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% for both params, so the baseline is 3. The description lightly maps them ('one token' -> address, 'at your size' -> usd) but adds no format, unit, or constraint detail beyond 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?

The second clause states the concrete job: identify which PancakeSwap pool a single-token swap should route through at a given size and what it costs. It also gestures at the sibling boundary by calling this 'the free half' versus the 'paid half' that prices a whole rebalance. However, the metaphor-heavy opening ('Portfolio rebalancing, the free half') delays the actual verb+resource, and the tool's own name ('best_route') is never restated in plain terms.

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?

Usage is only implied through the free-half/paid-half contrast: this tool for a single swap quote, the sibling for a whole-rebalance price. It never names rebalance_plan or states an explicit 'use this when / not when' condition, so the agent must infer the split.

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

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

Annotations mark this readOnlyHint=true and openWorldHint=true, and the description adds real context beyond them: it discloses that the call returns pricing terms and that the actual answer is sold via x402/escrow. However, phrasing like 'the swaps that move a BSC portfolio' and 'transfer tax measured from executed trades' creates ambiguity about whether it executes swaps at all, which is left unresolved.

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 long, run-on passage that is not front-loaded and forces the reader to reconstruct the purpose from scattered clauses. Several sentences are tangled and hard to parse, so the volume does not earn its place.

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 burden of describing returns; it partially does this ('cost as a share of the money moved,' 'names the holding the bill is concentrated in'). It is still vague about the actual return shape and the resolution flow, leaving gaps for a tool whose sole input is an open-ended task string.

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?

With 100% schema description coverage on the single parameter, the schema already documents it ('What you want, with the address in it'). The description only echoes the address requirement and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 gestures at a specific action (planning a portfolio rebalance) priced against pools, but the intent is buried under jargon like 'the paid half (0.10 USD1, or half that in $BOBAI)' and never resolves cleanly into a verb+resource statement. It never distinguishes itself from the sibling pancakeswap_best_route, so an agent cannot tell the two apart without deeper inference.

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 explicit when-to-use or when-not-to-use guidance relative to pancakeswap_best_route. The text discusses payment mechanics (x402, ERC-8183 escrow) rather than the conditions under which this tool is the right choice.

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