okx_get_orderbook

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

The tag '[L:READ]' hints at read-only behavior, but this is not formally defined as an annotation. No disclosure of rate limits, data freshness, or response structure. With no annotations, the description should carry more weight but provides minimal transparency.

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 extremely brief but not useful. It wastes characters on internal tags ('[L:READ] CAT:[行情]') and a mysterious prerequisite call. Conciseness should prioritize clarity, not just brevity.

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 80+ sibling tools, a clear description is critical. This description provides zero context about data returned, depth parameter usage, or how this tool differs from other order book tools. No output schema compounds the issue.

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 all 2 parameters with descriptions (e.g., '深度档位，默认20，最大400'). The description adds no extra semantic value beyond the schema, but with 100% schema coverage, 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 is just a tag '[L:READ] CAT:[行情]' and a note to call agent_catalog first. It does not state that this tool retrieves an order book. While the name 'okx_get_orderbook' is clear, the description itself fails to articulate 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?

No guidance on when to use this tool versus siblings like 'okx_get_books_full' or 'okx_get_spread_orderbook'. No prerequisites or alternatives are mentioned beyond the vague '请先调用 agent_catalog'.

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