Get cross-chain swap quotes

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

Annotations already declare readOnlyHint and openWorldHint. The description adds value beyond that: it explains the racing behavior, the ~25-second latency, that it returns both the best route and all routes sorted by net output, and the relationship to build_swap_tx. No contradictions with annotations.

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?

Four sentences, all carrying weight: purpose, read-only safety, amount units, and quoteId integration / timing. Purpose is front-loaded; no filler or repetition.

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?

With no output schema, the description explains the return shape at a high level (best route + all routes sorted, quoteId) and covers latency and safety. It could detail the route object structure or error cases, but given the strong annotations and 100% schema coverage, only a minor gap remains.

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?

Input schema has 100% description coverage, so the baseline is 3. The description repeats the amount-unit detail already in the schema ('Amounts are in the source token's smallest unit') and adds no new meaning for parameters like slippage, fromChain, or userAddress.

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 and resource: 'Race the BazaarSwap routing backend for cross-chain swap quotes' and states the exact output (best route plus every route, sorted by net output). It differentiates from build_swap_tx by noting the returned quoteId feeds that tool.

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 gives clear context: read-only, no funds moved, quoteId feeds build_swap_tx, and a ~25s race duration. However, it does not explicitly name alternatives or state when NOT to use this tool, so it stops short of the 'explicit when/when-not/alternatives' bar.

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