okx_get_open_interest_history_rubik

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

No annotations provided; the description only adds '[L:READ]' implying read-only, but does not elaborate on auth needs, rate limits, or other behavioral traits. The prerequisite dependency is mentioned but insufficient.

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?

While extremely short, it lacks substance and does not earn its place; it is under-specified rather than concise. Every sentence should contribute, but here the description is minimal and uninformative.

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 three parameters, no output schema, and no annotations, the description should compensate but fails to explain purpose, return values, or behavior. Only mentions a prerequisite call.

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% with descriptions for each parameter; the description adds nothing beyond the schema. Baseline of 3 is appropriate since schema already documents parameters.

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?

Only has '[L:READ]' and 'CAT:[统计]' which hint at permissions and category, but does not state what the tool does. The name implies retrieving open interest history, but the description itself is missing a clear verb and resource.

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?

No guidance on when to use this tool versus alternatives like 'okx_get_open_interest'. The only direction is to call agent_catalog first, which is a prerequisite, not usage context.

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