dragonswap_get_route

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

No annotations are provided, so the description must carry behavioral transparency. It indicates a read-like operation (getting a route) and mentions multi-hop, but does not disclose if it modifies state, requires authentication, or has rate limits. The description is vague about potential side effects or requirements.

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 a single sentence that is clear and direct. It could be slightly improved by structuring with a bullet or separating the multi-hop note, but it is concise and front-loads the key purpose.

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?

Given the 4 parameters and no output schema, the description could be more complete. It explains the tool's main function but omits output details, error cases, and performance characteristics. While adequate, it leaves room for improvement.

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% coverage with detailed descriptions for all parameters. The description adds the context of multi-hop but does not elaborate on parameter usage beyond what schema provides. Baseline score of 3 is appropriate as schema already handles semantics.

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 the best routing path' and specifies the resource 'swapping tokens' on 'DragonSwap V3 DEX'. It distinguishes from siblings like dragonswap_get_pool_info and dragonswap_get_quote by focusing on routing path rather than pool details or a simple quote.

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 mentions 'supports multi-hop for better prices', implying use when a multi-hop path might yield better rates, but does not explicitly state when to use this tool versus alternatives like dragonswap_get_quote. No exclusion criteria or when-not-to-use guidance is provided.

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