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

Annotations only declare readOnly and openWorld; the description adds material behavior beyond that: single-value output with no book or history, a $0.002 USDC charge per successful call, x402 payment via Base/Solana/Arc, and the important fact that failed calls are not charged. Cost and billing-failure semantics are exactly the kind of context annotations cannot convey.

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 purpose, then scope limit, then alternatives, then pricing. Semicolon-heavy but every clause carries information; the dense pricing sentence is long yet earns its place since cost is not in any structured field.

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?

Output schema exists, so return values need no prose. For a one-parameter read tool, the description covers scope, alternatives, and payment/completion semantics — nothing an agent needs to call it correctly is absent.

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% and the single symbol parameter is already documented with the same BTCUSDT/ETHUSDT style examples the description uses. The description adds no format constraints (case sensitivity, separator rules) beyond the schema, so baseline 3 applies.

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?

Names a specific verb+resource (Binance spot last price), scopes it to one trading pair with a concrete example (BTCUSDT), and explicitly bounds the output: 'Only the last price is returned; no order book or history.' That boundary alone separates it from crypto_binance_orderbook_depth without opening either schema.

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 routes two alternatives with their triggering conditions: orderbook_depth for a book snapshot with best bid, tao_alpha_prices for alpha token price/pool liquidity/reserves. What's missing is any guidance against the many other exchange-price siblings (finance_bitfinex_tickers, finance_coinbase_exchange_products, etc.), so an agent still has to infer why Binance spot rather than another venue.

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