Create 8DX Swap Calldata

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states the tool is non-custodial, non-signing, and non-sending, which are important safety traits. However, it does not explain whether it performs network calls, what the calldata output looks like, or how permit/slippage/simulation parameters affect behavior.

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 two sentences, front-loads the core purpose, and uses the second sentence to state critical exclusions. Every clause earns its place with no wasted words.

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?

For a complex tool with 9 parameters, nested objects, no output schema, and no annotations, two sentences are insufficient. It lacks guidance on how to obtain a 'quoted path,' how the permit flow works, what the calldata is used for next, and any failure/edge-case behavior.

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 description coverage is only 33%, and the tool description adds no parameter-level meaning beyond referencing 'a quoted path.' It does not explain slippageBps, skipSimulation, usePermit, or fromAddress, leaving the agent to infer their semantics from names alone.

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 and resource: 'Creates swap calldata from a quoted path.' It also clarifies what the tool does not do (sign, send, custody), which distinguishes it from transaction-sending and signing siblings like eightdx_wallet_send_transaction and eightdx_local_sign_and_send_transaction.

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 'from a quoted path' implies usage after eightdx_get_quote, and the explicit negative constraints ('does not sign... does not send... does not custody') provide some when-not guidance. However, it does not explicitly name alternatives or state when to prefer this tool over preview_market_swap or create_limit_order.

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