okx_get_spread_orderbook

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

Annotations are absent; the description only has '[L:READ]' indicating read-only. No mention of data freshness, permissions, rate limits, or other behavioral traits. The description carries full burden but adds minimal transparency beyond the read hint.

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?

Very short, but cryptic and includes non-English. It is concise but not effectively structured for clarity. The prerequisite call instruction adds value but the overall message is unclear.

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?

Tool is complex (spread orderbook with depth) and has many siblings, yet the description lacks explanation of what a spread orderbook is, how depth works, or how it differs from okx_get_spread_books. No output schema, so description should compensate but fails.

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%, and the description adds no additional parameter meaning. Baseline of 3 is appropriate as the schema already describes the two parameters adequately.

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?

Description is cryptic: '[L:READ] CAT:[策略-价差]' does not clearly state the tool's purpose. It hints at reading spread orderbook but lacks an explicit verb+resource statement. Additionally, it tells to call another tool first, confusing the purpose.

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?

Only guideline is '→ 请先调用 agent_catalog', which is minimal and does not explain when to use this tool over siblings like okx_get_spread_books or okx_get_orderbook. No exclusions or context provided.

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