okx_get_spread_books

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

With no annotations provided, the description carries full burden for behavioral transparency. It only indicates a read operation but lacks any information about side effects, authentication needs, rate limits, or data characteristics.

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 concise, consisting of a single line with tags and a prerequisite note. While not verbose, it lacks substantive content and could be more informative without sacrificing conciseness.

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 complexity of the domain with numerous sibling spread tools and no output schema, the description is severely incomplete. It fails to explain what data is returned, how to use the response, or how this tool fits into a workflow.

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?

The input schema covers the single required parameter with a clear description in Chinese. The tool description adds no additional meaning beyond what the schema already provides, so it does not improve parameter understanding.

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 minimal, using tags '[L:READ] CAT:[策略-价差]' to hint at a read operation for spread books, but it does not clearly define what 'spread books' are or differentiate from sibling tools like okx_get_spread_orderbook or okx_get_spreads.

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 includes a prerequisite hint '请先调用 agent_catalog', but provides no guidance on when to use this tool versus the many other spread-related tools, nor does it explain the context in which this tool is appropriate.

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