dex_plan_remove_liquidity

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

The description mentions 'single-use' and 'plan', suggesting a one-time operation that creates a plan. However, without annotations, there is no detail on side effects, permissions, or reversibility. It provides some behavioral context but not enough for a complex tool.

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 a single short sentence, which is efficient but under-informative. It sacrifices clarity for brevity, leaving out important context.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description fails to cover essential aspects like how to use the plan, what it returns, or constraints. It is incomplete for reliable agent invocation.

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%, and the description provides no explanation of any of the 7 parameters (account, token_a, token_b, liquidity, recipient, slippage_bps, deadline_minutes). The agent has no semantic help beyond parameter names and types.

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 'Issue a single-use removeLiquidity plan', indicating the verb and resource. It distinguishes from sibling tools like 'dex_plan_add_liquidity' and 'dex_plan_swap'.

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 guidance is provided on when to use this tool over alternatives, nor are there any prerequisites or exclusions mentioned. The agent must infer usage from the name alone.

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