dex_plan_add_liquidity

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

The description says 'single-use' and mentions 'exact calls, digest, and expiry' but does not clarify if this creates a plan that must be executed separately, or if it performs the actual addition. It fails to disclose whether it is a read or write operation, and no annotations are provided to compensate.

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 vague sentence. While concise, it sacrifices clarity and fails to convey essential information, making it under-specified rather than efficiently informative.

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?

With no output schema, 0% schema coverage, and no annotations, the description is critically incomplete. It does not explain the return value, the plan lifecycle, or how to use the tool effectively for a complex operation.

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 explanations for any of the 8 parameters (e.g., token_a, slippage_bps, deadline_minutes). The meaning of parameters is left entirely to the schema, which lacks descriptions.

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 it issues a single-use addLiquidity plan with exact calls, digest, and expiry, which clearly indicates the action and resource. However, it does not explain the context (e.g., DEX) or differentiate it from sibling tools beyond the name.

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 on when to use this tool versus alternatives like dex_plan_remove_liquidity or dex_plan_swap. No prerequisites or conditions are mentioned.

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