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

Annotations include readOnlyHint=true, and the description aligns with that (no contradiction). The description adds interpretive behavioral context (premium ratio, not absolute price) beyond annotations, but it doesn't detail response structure or pagination. The 'detail' parameter's token-saving behavior is mentioned in the schema, not the description. Adequate but not rich.

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?

Description is two sentences: first states the tool's purpose and core semantics, second provides a cautionary interpretation note. Every sentence earns its place, no fluff, front-loaded with the critical distinction.

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 read-only data retrieval tool with 100% schema coverage and no output schema, the description covers the essential purpose and interpretation trap. It could be improved by noting that 'full' detail returns raw arrays, but that's in the schema. Overall adequate for the 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 the baseline is 3. The description adds semantic value by explaining the meaning of the data (premium ratio) which aids understanding of symbol/interval usage, but it doesn't add syntax details for parameters beyond the schema. The description's focus on interpreting results adds value beyond schema.

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 candlestick data for the PREMIUM INDEX (difference between mark and index price), a key funding rate component. It explicitly distinguishes the value as a premium ratio, not absolute price, differentiating it from siblings like binance_get_klines or binance_get_mark_price_klines.

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 funding rate analysis (premium positive = funding tends positive) and notes the interpretation caveat, which helps agents decide when to use it. However, it doesn't explicitly name alternative tools or state when not to use it, but the 'jangan dibaca seperti candle harga biasa' gives clear context.

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