okx_get_spread_trades

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

The '[L:READ]' tag hints at read-only behavior, but with no annotations provided, the description should disclose other traits like authentication, rate limits, or side effects. It does not, leaving significant behavioral uncertainty.

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, but it does not waste words. However, it lacks a clear purpose statement, so the conciseness comes at the cost of completeness. It could be more informative without being verbose.

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's complexity (many sibling spread tools, no output schema, two parameters), the description is grossly incomplete. It fails to explain what the tool returns, when to use it, or how it differs from alternatives, leaving the agent without crucial context.

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% for the two parameters, so the description does not need to add parameter details. It adds no extra meaning beyond the schema, fitting the baseline.

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 consists only of tags ('[L:READ]', 'CAT:[策略-价差]') and a prerequisite note. It does not explicitly state that the tool retrieves spread trades, leaving the agent to infer purpose from the tool name alone.

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 only guidance is to call agent_catalog first. No information is given about when to use this tool versus alternative spread tools (e.g., okx_get_spread_ticker, okx_get_spread_orderbook), failing to differentiate among many similar siblings.

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