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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does add real context: the tool bundles approval, refund and cleanup steps, can initialize a pool at initial_tick, and requires a swap-then-recheck-then-mint ordering. It never explicitly says it returns unsigned transactions rather than broadcasting, which is the one behavioral fact an agent most needs confirmed for a 'prepare' tool.

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 front-loaded with the core action, then layers the tick-math caveat and the ordering rules, each sentence adding a distinct constraint. Some sentences are long and the 'See ekubo://docs/lp-position-workflow' pointer is good but arrives after dense prose, so it is efficient rather than optimally skimmable.

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 14-parameter, nested-object tool with an output schema, the description covers the hard parts: pool initialization, tick scaling, swap-before-mint ordering, and single-sided sizing from measured balances. Gaps remain around mode selection and the pool_id/pool_key and token_id conditions, which are only partially handled by the schema.

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 coverage is 79%, so the baseline is 3. The description adds genuine meaning for the otherwise undocumented tick_lower/tick_upper by giving the base-1.000001 conversion and warning that a 1.0001 calculation is 100x too small, and it ties the token ratio to the range and current price. It says nothing about mode, token_id, pool_initialized, initial_tick or slippage_bps beyond what the schema already states.

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: preparing a v3 position mint or add_liquidity, including optional pool initialization, approvals, refunds and cleanup. It is clear what the tool produces. It does not explicitly differentiate itself from sibling preparers such as prepare_uniswap_v3_add_liquidity or prepare_pool_initialization, leaving the agent to infer that this is the Ekubo-specific variant from the ekubo docs reference.

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?

Strong procedural guidance: do every swap first, re-read the tick with the pool's current_state_query, then mint once; execute a missing-side swap separately and size the deposit from the measured balance after receipt, never a quoted output. What is missing is selection guidance between mode=mint_new and add_liquidity, and when to pick this tool over the Uniswap add-liquidity siblings.

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