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

Goes well beyond readOnlyHint/openWorldHint by disclosing the paid-call model: $0.002 USDC per successful call, x402 payment across Base, Solana or Arc, and that failed calls are free. Cost and payment-rail facts are exactly the kind of behavior an agent cannot infer from annotations and could otherwise stumble into.

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 and scope, then routing, then pricing — a sensible order with no filler sentences. The sibling enumeration is slightly padded (repeating "when you need ... for one pair" and field lists) for tools that differ only by exchange, but every clause carries information.

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?

For a one-parameter, read-only ticker lookup with an output schema, annotations, and a 100%-covered input schema, nothing material is missing: source, scope limits, alternatives, and billing are all covered. Return values are handled by the output schema, so the description needn't explain them.

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 BTCUSDT format in the schema. The description's example restates that without adding format rules, exchange-suffix conventions, or case sensitivity, 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?

States a specific resource and verb-equivalent: MEXC spot last price for one pair, with an example symbol and the source endpoint. It also bounds scope explicitly ("Last price only; no order book or history"), which lets an agent rule out this tool for depth or historical queries without opening the 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 to finance_bitget_tickers and finance_bitstamp_tickers with the condition that distinguishes them (different exchange), and states the exclusion "no order book or history." It stops short of naming the many other ticker siblings on this server (e.g. finance_binance_prices, finance_huobi_tickers), so the routing is partial rather than exhaustive.

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