Preview 8DX Market Swap

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

With no annotations, the description carries the full burden and does disclose several return behaviors: quote data, a 30-second refresh hint, slippage/deadline metadata, route link metadata, and external signing guidance. It implies non-mutation via 'Previews' but does not explicitly state that no on-chain transaction is sent or mention any side effects or prerequisites.

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 well-structured sentence that front-loads the core action and then enumerates the return value categories. Every phrase adds useful information without waste.

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 8 parameters, no annotations, and no output schema, the description lists key return outputs but falls short of explaining critical invocation context, such as optional parameters, required input formats, or whether a wallet connection is needed. It provides a useful outline but not enough to fully guide correct use.

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 description contains no parameter-level information, and schema description coverage is only 63%, leaving parameters like 'slippageBps' without any explanation. It does not compensate for the coverage gap by explaining relationships such as amountIn vs amountInWei or how the API format should be interpreted.

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 uses a specific verb ('Previews') and resource ('market swap'), clearly positioning it as a pre-execution step distinct from 'eightdx_create_swap'. However, it does not explicitly differentiate itself from the sibling 'eightdx_get_quote', relying on the phrase 'AI-guided flow' to imply additional context.

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 phrase 'for an AI-guided flow' gives some usage context, implying this tool is meant for a guided preview before a swap, but it does not explicitly state when to use it over alternatives like 'eightdx_get_quote' or when it should be skipped. No exclusions or alternative tool names are provided.

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