spectra_quote_trade

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

Discloses the quote method (on-chain get_dy() or math estimate), accuracy differences, and return contents including pool context and source indication. No annotations exist, so description fully covers behavior.

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?

Well-organized with front-loaded purpose, but slightly lengthy. However, every section adds value, so it's still highly effective.

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 no output schema, the description thoroughly explains return values (expected output, rates, pool context, etc.) and covers all necessary context for a quoting 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?

All 5 parameters have schema descriptions. The tool description adds extra meaning, such as defining side meanings ('buy' vs 'sell'), explaining slippage formula, and clarifying amount units.

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 the tool estimates expected output, price impact, and minimum output for a PT trade. It distinguishes from YT and mentions specific sibling tools for alternatives.

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?

Explicitly explains when to use on-chain vs fallback, and suggests alternatives like spectra_simulate_trade and spectra_compare_yield for additional context.

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