dex_plan_swap

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

With no annotations, the description must fully disclose behavior. It hints that the plan is single-use and involves a fresh quote, digest, and expiry, but fails to explain side effects, permission requirements, or whether it executes or only plans. The behavioral profile is vague.

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 sentence, which is concise but lacks structure. It is front-loaded with the verb but sacrifices informative content for brevity.

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 (11 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain what the plan object is, what the return value contains, or prerequisites like needing a prior quote, making it insufficient for correct 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?

The schema has 0% description coverage, yet the description does not explain any of the 11 parameters. The words 'fresh quote, exact calls, digest, and expiry' do not map directly to parameter names, leaving the agent with no guidance on how to fill in fields like mode, path, slippage_bps, etc.

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 it issues a single-use DEX swap plan, distinguishing it from quote-only tools (dex_quote_exact_in/out) and liquidity plan tools (dex_plan_add_liquidity, dex_plan_remove_liquidity). The specific mention of 'fresh quote' and 'exact calls' further clarifies its purpose.

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 implies usage for creating a swap plan but does not explicitly state when to use this tool versus alternatives like dex_quote_exact_in/out or simulate_transaction. No exclusions or prerequisites are mentioned.

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