sideswap_quote

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

Description labels the tool as 'read-only', implying no state change. No annotations provided, so description carries full burden. It discloses the mutual exclusivity constraint and does not contradict any 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?

Two concise sentences: first states purpose, second gives critical usage instruction. No unnecessary words, front-loaded with key 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?

Covers main behavioral aspects (read-only, mutual exclusivity, usage order). With no output schema, it could mention the return format (e.g., quote details), but it is sufficient for a simple quote 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 80%. Description adds value by clarifying mutual exclusivity of send_amount and recv_amount, which is not obvious from schema alone. However, it does not provide additional semantics for the other parameters beyond what schema offers.

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?

Description clearly states 'Get a read-only price quote for a SideSwap Liquid asset swap', specifying verb and resource. It distinguishes from sibling sideswap_execute_swap by noting it should be used before that 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?

Provides clear usage instructions: 'Provide exactly one of send_amount or recv_amount' and 'Use this BEFORE sideswap_execute_swap'. Gives context on when to use, but does not explicitly list alternatives or when not to use.

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