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

The description goes well beyond the annotations by explaining that it compares all available rails, ranks by net rate, returns Top-5 results, and provides ready-to-execute parameters. It also notes that own rails win on same-chain routes, adding behavioral nuance consistent with readOnlyHint=true and destructiveHint=false.

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 ('Universal crypto router'), and packs meaningful differentiators—aggregator types, chain coverage, ranking logic, and execution-readiness—without 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?

With no output schema, the description adequately explains the return shape: best result plus Top-5 in results[] with ready-to-execute params. It also covers the key selection criteria and route breadth. A small gap is the lack of detail on result fields or failure behavior, but overall it is sufficiently complete for a routing tool.

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 100% for from, to, and amount, so the schema already documents parameter meaning. The description does not add parameter-specific details beyond confirming that swaps can include hard/exotic pairs, so a baseline score of 3 is appropriate.

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 states a specific function: 'compares ALL rails in one call' and clearly differentiates this router from sibling swap tools by covering Solana, EVM, and cross-chain providers in a single routing call. It also specifies the output: ranks by best NET rate and returns best + Top-5 results.

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 usage context: 'Use for any swap incl. hard/exotic pairs.' It implies this tool is the broad comparison router versus single-chain swap tools, but it does not explicitly name alternatives or state when not to use it. Still, the guidance is strong enough for an agent to select it appropriately.

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