cpu_quote_buy

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

Fully describes read-only nature, no transaction, session requirement. Discloses transit fee re-quoting with ~10% headroom as ceiling, not extra charge. No annotations, so description bears full burden and does so excellently.

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-structured with front-loaded purpose. Contains valuable details but is slightly lengthy; still every sentence adds value.

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 behavior, parameters, return values, and comparison to sibling. Completing the lack of output schema by describing returns. For a complex preview tool, it is fully adequate.

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 parameters have schema descriptions (100% coverage). Description adds meaning by explaining chain as waypoints for transit fees, and returns (sale, transitFee, total) beyond 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?

Clearly states it's a read-only preview for buying from a lot, reserves nothing, sends no tx. Distinguishes from sibling cpu_buy_lot by advising use before it.

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?

Explains two usage modes: with chain for exact total, without for seller-only estimate. Explicitly says 'use before cpu_buy_lot', providing clear when-to-use and alternative.

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