sodax_get_solver_oracle

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

The description richly discloses behavioral traits beyond the annotations: chainId compatibility check and rejection behavior, routability caveats with specific token examples, and the fact that being listed does not guarantee a swap route. This compensates for the lack of detailed 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?

The description is front-loaded with the core purpose and adds valuable caveats in a later sentence. It is longer than minimal but each part serves a purpose (usage, limitations, examples). Could be slightly more concise without losing meaning.

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 lacks explicit details about the return structure (e.g., list of objects with price, token, chain). Given no output schema and the tool's importance for quoting, this is a gap. However, the purpose is clear and usage guidance compensates somewhat.

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%, but the description adds significant meaning: explains why chainId='146' is special, that symbol filter is case-insensitive exact match, and that 'json' format returns raw data. These enrich the parameter understanding.

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 it gets 'the solver's oracle USD prices per (chain, token)', with specific filtering options. It relates to sodax_get_solver_quote for quoting, which helps distinguish from sibling tools. However, it could more explicitly differentiate from other 'get' tools like sodax_get_hub_assets or sodax_get_swap_tokens.

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 specific usage guidance: use for quoting with sodax_get_solver_quote, filter by chainId='146' for compatibility, and sanity-checking quote amounts. It includes caveats about routability and which tokens work best, but does not explicitly state when not to use it.

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