Spot quote

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

Beyond annotations (readOnlyHint=true, destructiveHint=false), description adds 'Never mutates state,' 'Paper trading only,' 'virtual funds (50,000 mUSD),' and 'Price age is informational only.' No contradiction with 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?

Concise, front-loaded with the core purpose. Every sentence adds necessary information without redundancy. No fluff.

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 the tool's complexity (4 params, nested objects, output schema exists), the description covers read-only usage, prerequisite resolve_symbol, paper trading, and informational price age. Output schema explains return values, so no gap.

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 coverage 100% provides baseline 3. Description adds critical context: 'coinId is a UCID, NOT a ticker — use resolve_symbol first.' Also clarifies side effect ('buy increases the coin balance'). Adds value 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?

The description clearly states it is a 'Read-only spot MARKET quote' that provides live execution price, estimated cost, balance, and fill eligibility. It distinguishes from siblings like place_spot_order and other quote tools (futures_quote, pm_quote).

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 instructs to 'quote before place_spot_order instead of buying/selling blind.' Mentions paper trading and virtual funds, indicating the context. Could be more explicit about when not to use, but clear enough.

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