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

With no annotations provided, the description carries full disclosure burden and does so thoroughly: it explains the swap of half the USDC, minting of a full-range Uniswap v4 position to the caller, refund of leftovers, non-custodial nature, removal path, mode-dependent behavior, and the price-check condition. This goes well beyond a minimal description.

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 dense but efficiently structured: the deposit action leads, followed by removal, then the read-mode distinction and the price warning. Every sentence earns its place, and there is no filler or restatement of the tool name.

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 single optional parameter tool with no annotations and no output schema, the description provides enough context to call it correctly: what it does, how to use it, what changes with the parameter, and when not to act. Nothing essential is missing.

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?

Although the schema covers the optional address parameter, the description adds meaningful semantics by explaining what happens with and without it: with an address it returns positions/deposit/value; without it returns the contract, ABI, steps, and price comparison. This gives an agent actionable parameter behavior 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 description states a specific action, resource, and scope: putting USDC to work in the APEX/USDC pool on Arc via the ArcGrow contract. It is clearly distinguishable from sibling tools like arc_pools or arc_market because it names the exact contract method, the pool, and the non-custodial mechanism.

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?

The description gives clear operational guidance: deposit with USDC as native value, remove liquidity via the PositionManager methods, use an address to read positions, and avoid depositing when the price divergence exceeds 10%. It does not explicitly name sibling alternatives or exclusions, but the usage context is unambiguous.

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