okx_get_spread_orders_history

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

The [L:READ] label hints at read-only behavior, which is useful, but there is no disclosure of other behavioral traits such as authentication, rate limits, or return format. The prerequisite is mentioned but not elaborated.

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 (under 20 words) and uses a structured prefix for read-only and category. However, it could be more informative without losing 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 tool has parameters, no output schema, and many siblings, the description lacks details about return values, parameter usage, and when to use this tool over similar ones. The prerequisite is helpful but incomplete.

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 description coverage is 100% with both parameters described in Chinese. The tool description adds no extra 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 does not explicitly state what the tool does. It only provides a category and a prerequisite, leaving the purpose to be inferred from the name. This is vague for an agent that may not understand the context.

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 provides a single usage guideline: call agent_catalog first. It does not differentiate when to use this tool over sibling spread tools like okx_get_spread_orders or okx_get_spread_orders_pending.

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