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

With no annotations, the description carries the full burden and does well: non-custodial, from your own key, leftovers refunded, nothing kept, position minted to the caller, and a self-imposed refusal condition when prices diverge. It omits failure modes, gas/slippage behavior beyond the price guard, and what a minted position looks like on error, so not fully exhaustive.

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 action is front-loaded, but the body is a single semicolon-chained block mixing deposit mechanics, exit instructions, return shapes, and the price guard. Every clause earns its place informationally, yet the lack of structure makes it harder to parse than it needs to be.

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, and the description compensates by describing both return modes (positions/deposit/value with an address; contract/ABI/steps plus priceCheck without). Covers what an agent needs to call it safely, though error behavior and the exact shape of positions data are unstated.

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 100% so the baseline is 3, but the description adds real meaning: with {address} the tool returns that address's positions, deposit and current value; without it, it returns the contract, ABI, steps, and priceCheck. That dual-mode semantics of the optional parameter is not derivable from the schema text alone.

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 verb and resource — deposit USDC into the APEX/USDC pool on Arc (eip155:5042) via grow(minApexOut) on the ArcGrow contract — plus the mechanics (half swapped, full-range v4 position minted to caller, leftovers refunded). This is clearly distinguishable from the other arc_* tools, none of which deposit into a pool.

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?

Gives explicit operational conditions: deposit only when the APEX price on Arc is within 10% of its X1 price, otherwise refrain because half the USDC would buy at a premium. It also names the exit route (PositionManager with DECREASE_LIQUIDITY or BURN_POSITION + TAKE_PAIR). It stops short of pointing at a sibling tool for the read-only yield or price checks it references, so no explicit alternative routing.

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