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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions returning 'human-unit amounts, the guaranteed minimum, every fee line, route stats, and blockers' and the API key requirement, but does not indicate side effects (likely none), rate limits, or idempotency. For a quote tool, this is acceptable but not comprehensive.

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, using four short sentences. It is front-loaded with the core purpose, followed by key details. There is no redundancy or unnecessary information.

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 complexity (8 parameters, no output schema), the description explains return content and a critical parameter format. However, it omits how the quote connects to other tools (e.g., building a transaction), default values (chainId, gasless), and does not fully replace a missing output schema by detailing all return fields.

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 high (75%), and the description adds useful context by explicitly stating that sellAmount is a 'HUMAN decimal like "0.01", never raw units'. It also overviews return fields, which compensates for any missing parameter details and enhances understanding beyond the schema.

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 best-execution swap quote from Rialto', specifying the verb, resource, and purpose. It distinguishes from sibling tools like rialto_build_unsigned_tx and rialto_preflight by focusing solely on quoting.

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 the required API key and clarifies that sellAmount must be in human units. However, it does not explicitly state when to use this tool versus alternative tools like rialto_preflight or rialto_build_unsigned_tx, nor does it provide guidance on prerequisites beyond the API key.

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