removeLiquidity

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

Discloses rate limit (5 req/s) and behavior for removeRate and removeType parameters. However, without annotations, it does not disclose side effects, required permissions, or failure states for a withdrawal operation. Adequate but not comprehensive.

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 concise paragraphs front-load purpose and cover optional parameter semantics with no redundant words. Every sentence adds value.

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 provided. Description covers optional parameters but omits required ones and return value. For a financial withdrawal, more context (e.g., post-withdrawal state, error conditions) would improve completeness.

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 0%, so description compensates well by explaining removeRate (integer percentage 1-100, omitting or 0 means 100% full redemption) and removeType (defaults to Normal, proportional redemption). However, it does not describe the three required parameters (productId, orderLinkId, positionId).

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 clearly states 'Withdraw funds from a Liquidity Mining pool position', specifying the verb (withdraw) and resource (Liquidity Mining pool position). This distinguishes it clearly from sibling tools like addLiquidity and executeLPRedeem.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., executeLPRedeem). The description implies usage context through parameter details but lacks when-not-to-use or alternative tool suggestions.

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