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

Despite annotations already covering the safety profile, the description adds substantial operational context the agent could not infer: it is an external-API spot read, it is rate limited, results should be cached, the returned venue/quote must be reported, and price_as_of/price_stale must be disclosed. It also spells out the access model (0.005 USDC via x402 PAYMENT-SIGNATURE header, or free with an API key) and the venue-selection fallback 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?

Front-loaded with the primary purpose and return contents, then usage, then constraints, which is the right ordering. It is denser than typical, with a bracketed access/pricing block that is useful but long; no sentence is truly wasted, but the block could be trimmed.

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, the description still enumerates what is returned (trade price, market cap, 24h volume, venue, quote, price_as_of, price_stale), covers rate limiting, caching guidance, auth/payment options, and fallback behavior. An agent has everything needed to call it correctly and interpret the result.

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 is 100%, so baseline is 3; the description goes beyond it by explaining the coupling rule — quote_token and market_data_venue must be passed together to honor a requested exchange, and when omitted the tool picks a supported market and returns its quote and venue. That is real semantic value not present in the per-field schema text, though 'provider' is left undiscussed.

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?

States a specific verb and resource — 'Latest trade price for a selected market, plus aggregate market cap and 24h volume' — which is concrete and tells the agent exactly what comes back. It implicitly distinguishes itself from historical/candle siblings by calling itself 'a spot reading' and by framing it around 'what an asset is doing now', though it never names a sibling explicitly.

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?

Gives clear usage context: 'Use it when the user asks what an asset is doing now, or when a live price is needed to ground a recommendation', plus a caching rule ('call it once per asset and reuse the answer'). It doesn't name a concrete alternative tool or exclusion case (e.g. use get_ohlcv for history), so it stops short of full routing guidance.

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