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

With no annotations, the description fully carries the behavioral burden. It discloses custody ('from your own key, non-custodially'), swap mechanics ('half is swapped for APEX'), minting ('full-range Uniswap v4 position minted to the caller'), refunds ('leftovers refunded, nothing kept'), and removal actions. This is exceptional transparency.

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?

Three dense sentences with no filler and the core action front-loaded. The first sentence is long and compound, but each clause contributes operational detail; a bit more formatting would make it perfect.

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?

No output schema exists, so the description is responsible for return-value explanation, and it does: positions, deposit, and value with an address; contract, ABI, and steps without. It also covers the exit path, making the tool self-contained for an agent.

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?

The schema already covers the address parameter, so a baseline of 3 applies. The description adds functional meaning beyond the schema by explaining exactly how omitting or including the address changes the result, which earns an extra point.

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?

States a specific action ('Put USDC to work in the APEX/USDC pool') with a precise contract call ('call grow(minApexOut) on the ArcGrow contract'), and distinguishes itself from siblings by describing the LP minting and read variant. This is far from a tautology.

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?

Clearly explains the two invocation modes ('With {address} this returns... without it, the contract, ABI and steps') and even includes removal instructions via PositionManager. It lacks an explicit 'use X instead' exclusion of sibling tools, but the context is strong enough to route an agent.

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