sideshift_quote

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

No annotations provided; description mentions fixed-rate and TTL (~15 min) but lacks details on quote expiration, idempotency, or error handling.

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 sentences, no redundancy, front-loaded with purpose and TTL.

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?

Provides essential usage flow and amount constraint, but lacks description of return value (quote object) and more detail on coin/network parameters.

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?

Clarifies exclusive relationship and decimal format for amount parameters (33% schema coverage), but no additional info for coin/network parameters beyond their names.

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?

Explicitly states it requests a fixed-rate SideShift quote with a TTL hint, clearly distinguishing from sibling tools like sideshift_send and sideshift_status.

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 explicit instructions: use exactly one of deposit_amount or settle_amount as decimal string, and use before sideshift_send to confirm quote.

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