dragonswap_get_quote

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

No annotations provided, so description carries full burden. It discloses token decimal behavior and naming flexibility, which is helpful. However, it does not reveal if the tool is read-only, error handling, rate limits, or other behavioral aspects beyond the noted token nuances.

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?

Two sentences: first clearly states purpose, second adds crucial token-specific exceptions. No redundant information. Efficient and well-front-loaded.

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?

No output schema, yet description does not mention what the quote returns (e.g., estimated output price, execution details). Parameter documentation is mostly in schema, but the tool's output and life cycle context (e.g., use before swap) are missing. Adequate but not comprehensive.

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 value by clarifying USDT uses 6 decimals (which may override auto-detect) and that stKAIA has alternative symbols. This aids parameter interpretation beyond the schema's 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 clearly states the action ('Get a quote'), the resource ('for swapping tokens'), and the specific DEX ('DragonSwap V3 DEX'). This distinguishes it from siblings like dragonswap_get_pool_info and dragonswap_get_route.

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 provides token-specific notes (USDT decimals, stKAIA naming) but does not explicitly state when to use this tool versus alternatives like dragonswap_get_route or when to use this as a prerequisite for a swap. Usage is implied.

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