okx_get_option_oi_expiry

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

Without annotations, the description must fully disclose behavior. It indicates a read operation via 'L:READ' but does not mention any required permissions, rate limits, error handling, or output format. The prerequisite hint is useful 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?

The description is very short but uses cryptic code-like prefixes that hinder readability. Important information (purpose, output) is missing, making it more confusing than concise.

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's simplicity (single param, no output schema), the description should clarify what data is returned (e.g., OI by expiry) and any grouping logic. The prerequisite note is helpful but does not cover the tool's primary function.

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 the schema already describing the 'ccy' parameter as required currency. The description adds no additional meaning, so baseline 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 uses cryptic metadata like 'L:READ' and 'CAT:[统计]' but fails to explicitly state that the tool retrieves option open interest by expiry. The name suggests this, but the description does not confirm, leaving the purpose ambiguous.

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 only guidance is '请先调用 agent_catalog' (call agent_catalog first), which is a prerequisite. No information is given on when to use this tool vs. siblings like okx_get_option_oi_strike or okx_get_option_open_interest.

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