Orca Open Position

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

Annotations indicate a mutation (readOnlyHint=false) that is not destructive. The description adds 'concentrated liquidity position' but omits side effects like token requirements, wallet approval needs, or position NFT creation. Behavioral traits beyond annotations are not disclosed.

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: first states purpose clearly. Second sentence about SAP tools is not directly relevant to this tool's usage, adding slight noise. Length is acceptable but could be more focused.

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?

Despite output schema existing, the description is too brief for a complex DeFi operation. Missing prerequisites (token balances, pool existence), workflow context, and potential outcomes. An agent would need additional knowledge to use this tool correctly.

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?

Input schema has 100% description coverage, so baseline is 3. The description does not add extra meaning to parameters (e.g., priceLower/priceUpper are only described as 'Price Lower parameter for Orca Open Position'). No value added beyond 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?

Title and description clearly state the tool opens a concentrated liquidity position on an Orca Whirlpool. This verb+resource combination distinguishes it from sibling tools like orca_swap, orca_closePosition, and orca_collectFees.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that it is for providing liquidity in a concentrated range, nor does it contrast with swap or closing positions. The SAP context note is about unrelated tool registration.

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