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

Annotations already declare readOnlyHint and openWorldHint. The description adds meaningful behavior: the default response is a concise summary (trend + <=10 latest points), while detail='full' returns complete history respecting limit. This clarifies output shape and token-saving behavior beyond the annotations. No contradictions.

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?

Two sentences, front-loaded with purpose, then usage and parameter behavior. Every sentence contributes; no filler.

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?

Despite lacking an output schema, the description explains the two output modes and their token implications, and provides an interpretation framework. It does not enumerate exact response fields, but the schema references docs/tool_response_reference.md for full detail. For a 4-parameter read-only tool, this is adequately complete.

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 baseline is 3. The description adds value by explaining the interaction between detail and limit, and clarifying that summary mode returns derived metrics plus a limited number of recent points. This goes beyond the schema's enum descriptions.

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 tool as retrieving Open Interest history to observe up/down trends, explicitly distinguishing it from the current-snapshot sibling binance_get_open_interest by emphasizing 'histori' and 'TREN'. The phrase 'LANGSUNG dari Binance native' adds source specificity. The verb is implicit but the resource and analytical purpose are unambiguous.

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 explicitly instructs combining this tool with binance_get_klines at the same period and provides an interpretive rule (OI up + price up = new entry; OI down + price up = short covering). It also advises using the default summary to save tokens, implying full detail only when needed. It does not state exclusions or alternative tools, so it falls short of a 5.

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