sodax_get_solver_quote

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds critical behavioral details: token address rejection with specific error message, the need to use hub-chain addresses, and the return of 'No path found' for failed routing. This significantly aids agent decision-making.

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 concise, uses bold 'IMPORTANT' to highlight critical details, and front-loads the purpose. Every sentence contributes meaningful information without redundancy.

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 description covers the tool's purpose, token address constraints, quote type meanings, and error behavior. It references a complementary tool (sodax_get_solver_oracle) for context. Given the absence of an output schema, it explains possible return values. Minor omission: no mention of the 'format' parameter, but it is optional with a default.

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 the description adds value by explaining tokenSrc/tokenDst address constraints and the meaning of quoteType. It provides context beyond the schema, such as the importance of using addresses from sodax_get_solver_oracle.

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 'Get a swap quote from the SODAX solver,' specifying the verb and resource. It distinguishes this tool from siblings by focusing on solver quotes and highlighting constraints unique to this 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 explains when to use the tool (to obtain a swap quote) and provides important prerequisites: token addresses must be hub-chain assets on chainId 146, and it directs users to sodax_get_solver_oracle for valid addresses. It also clarifies the two quote types. While it doesn't explicitly state when not to use it, the guidance is clear for common use cases.

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