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

With no annotations, the description carries the disclosure burden and does it well: it returns a deposit address, funds are custodial only at the venue during the swap, and blueDEX never holds funds. It does not cover failure/expiry behavior or auth/rate limits, so it is strong but not exhaustive.

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?

Three sentences with no filler: purpose, operational flow/return value, and custody model are each addressed in sequence. The ID lookup hint is a useful, non-redundant addition.

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?

The definition covers the core return value and the full user flow, plus the custody nuance, and there is no output schema to contradict. It leaves refund/expiry behavior to the schema, but the absence of status/fee details is a minor gap rather than a blocking one.

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 100%, so baseline is 3; the description adds meaning by explaining that `from` is sent to the returned deposit address and `to` settles to `settleAddress`. The instruction to use list_instant_assets for ids also clarifies parameter values beyond the schema examples.

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 opens with a specific verb ('Open') and resource ('INSTANT shift') and clearly scopes the tool to assets with no on-chain DEX route, listing Tron, BTC, and cross-chain. This distinguishes it from the swap/route siblings even without naming them.

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?

It states the selection condition: use this when there is no on-chain DEX route, for Tron/BTC/cross-chain assets. It also points to list_instant_assets for valid IDs. It does not explicitly name alternatives or when-not-to-use, but the context is clear enough for an agent to choose it.

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