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

Annotations declare readOnlyHint=true, which the description aligns with (read operation). It adds context about the data source (blended spot exchanges) and the critical distinction from transaction prices. It does not disclose rate limits or pagination behavior, but the readOnlyHint covers safety. The description adds value beyond annotations by explaining the underlying data semantics.

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 concise, two sentences, with a critical warning upfront and an example. It is front-loaded with the most important usage distinction (pair vs symbol). Slightly under-structures the parameter hints, but overall efficient.

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 has a complex parameter (`pair` with special semantics) and no output schema, the description covers the essentials: what data is returned, how to specify the pair, and the detail parameter for output size. It lacks explicit mention of time range behavior (startTime/endTime) but those are optional and self-explanatory from the schema. Overall complete for the tool's complexity.

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 description coverage is 100%, so baseline is 3. The description adds critical semantics for the `pair` parameter (explaining the difference from `symbol` and providing an example). It also clarifies the `detail` parameter (summary vs full, saving tokens) which goes beyond the schema. This justifies a score above baseline.

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 returns candlesticks of the INDEX PRICE (blended spot exchanges, basis for premium index/funding), explicitly NOT futures transaction prices. It distinguishes itself from sibling tools like binance_get_klines and binance_get_mark_price_klines by noting the 'pair' vs 'symbol' distinction and the index price nature.

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?

It provides important usage guidance: use `pair` without margin-asset suffix (e.g., BTCUSD vs BTCUSDT), and distinguishes this from regular symbol trading. However, it does not explicitly state when NOT to use this tool versus alternatives like binance_get_mark_price_klines or binance_get_premium_index_klines, though the differentiation is implied.

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