okx_get_option_oi_strike

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

No annotations are provided, and the description only indicates it is a read operation (L:READ). It does not disclose any behavioral traits such as data freshness, rate limits, or side effects, leaving the agent uninformed.

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, which is concise but at the expense of clarity. It lacks substantive content to be considered well-structured or front-loaded with useful information.

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 2 required params, no output schema, no annotations, and a minimal description, the tool is not contextually complete. The description does not explain return values or typical use cases, making it inadequate for effective agent invocation.

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 covers 100% of parameters with descriptions (ccy, expTime). The description adds no additional meaning beyond the schema, so baseline score of 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 is cryptic and does not explicitly state that this tool retrieves option open interest by strike. The name suggests it, but the description only says 'L:READ' and a category, which is insufficient to clarify purpose compared to siblings like okx_get_option_oi_expiry.

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 advises to call agent_catalog first, providing a prerequisite but no guidance on when to use this tool versus alternatives (e.g., okx_get_option_oi_expiry). No context for selection among siblings.

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