Spot quote

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

Discloses read-only nature ('Never mutates state'), paper trading only with virtual funds, and that price age is informational. No annotations provided, so description fully covers behavioral traits.

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?

Four sentences, front-loaded with core purpose. Every sentence adds value; no redundancy. Efficient yet comprehensive.

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?

With no output schema, description fully explains return fields, preconditions (coinId via resolve_symbol), and paper trading context. Complete for a 3-param 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 covers 67% of parameters with descriptions; description adds crucial context for coinId (UCID, need resolve_symbol) and implies side/quantity usage. Does not elaborate on side enum or quantity format 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 spot MARKET quote, listing specific outputs (live price, estimated cost, balance, fill eligibility). Distinguishes from siblings like futures_quote and pm_quote, and contrasts with place_spot_order.

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 tells when to use: 'quote before place_spot_order instead of buying/selling blind.' Also instructs to 'use resolve_symbol first' for coinId, providing a clear precondition and alternative.

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