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

Annotations already declare readOnlyHint=true, so the safety profile is supplied. The description adds real context beyond that: it is a multi-phase workflow and 'the wallet never constructs a route or transaction', clarifying the division of responsibility between tool and client. It does not say whether the produced approvals are bounded, whether phases must be executed in one session, or what the response contains.

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?

Two sentences, front-loaded with the workflow name and then the phase sequence, with no filler. It is dense with domain jargon ('interface-equivalent', 'phased') that costs some readability, but nothing is redundant.

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 9 parameters, a nested quote_result object, and an output schema, the description covers the workflow shape but leaves out the operational glue: which sibling produces the quote result, where pending_current_sqrt_ratio is read from, and what the caller does with the returned calldata phases. Adequate as a pointer, thin for a tool this complex.

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 78%, so the baseline is 3. The description does map loosely onto the key inputs — 'pending pool-price read calldata' corresponds to pending_current_sqrt_ratio, 'router quote calldata' to the nested quote_result object, and 'target-price execution' to target_price — but it gives no format, sourcing, or constraint detail, and swap_deadline_minutes is only explained 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?

The description states a specific verb and resource: it runs a 'phased fix-price workflow' to prepare a pool price correction, and it clarifies that it emits calldata rather than building a route itself. It stops short of naming or contrasting any sibling (e.g. get_quotes_with_plans, prepare_uniswap_reads), so the agent must infer where this sits in the prepare_* family.

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 implied through the stated phase order — pending pool-price read calldata, then router quote calldata, then approvals and target-price execution — which tells the agent this is a multi-step flow. There is no explicit 'use this when…' statement, no prerequisites (where quote_result or pending_current_sqrt_ratio must come from), and no guidance on when not to use it.

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