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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds meaningful behavioral context: it costs $0.001 USDC per call and is byte-identical to a specific REST endpoint. These details go beyond the structured annotations and clarify cost and exact data provenance.

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?

The description is compact and front-loads the main purpose, then adds cost and endpoint identity. The list of statistics is dense but useful, and there is no filler. It could be slightly shorter, but every sentence earns its place.

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 a single well-documented parameter, a provided output schema, and safety annotations, the description does not need to explain return values. It adds the important cost and byte-identical endpoint details, making the tool's behavior sufficiently complete for correct invocation.

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 the symbol parameter is already fully documented with format and examples. The description adds no additional parameter-level meaning beyond calling it a symbol, but the schema is sufficient, so the baseline score of 3 is appropriate.

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 identifies the resource as KuCoin's 24h statistics for a symbol and enumerates the returned fields (last, bid/ask, high/low, volume, fees). It does not use an explicit verb like 'get' or 'fetch', but the intent is unambiguous and the exchange scope distinguishes it from other market tickers.

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?

The description implies usage for KuCoin 24h market data by naming the data source and the fee rates, which helps differentiate it from a best-quote tool. However, it does not explicitly state when to choose this over sibling tickers like market_gate_ticker or market_kucoin_best_quote, nor does it mention when not to use it.

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