okx_get_spread_orders_pending

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

No annotations are provided, so the description must disclose behavioral traits. It hints at read-only ('L:READ') but does not explicitly confirm no side effects. Missing details on authentication, rate limits, or any other behavioral considerations.

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 short but poorly structured for readability. It uses non-standard formatting (brackets, arrows) that may confuse an agent. It sacrifices clarity for 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?

For a simple tool with one parameter, the description should clarify what 'pending' means in this context (e.g., unexecuted orders). It fails to explain the scope or default behavior, leaving gaps despite low complexity.

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 already describes the sprdId parameter as 'spread contract ID' (100% coverage). The tool description adds no additional context about the parameter, so it meets the baseline of 3 without enhancement.

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 uses cryptic tags ('L:READ', 'CAT:[策略-价差]') and does not explicitly state the tool's purpose. It fails to clearly indicate that this tool retrieves pending spread orders, leaving the agent reliant on the 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 description includes a prerequisite ('please call agent_catalog first') but provides no guidance on when to use this tool versus siblings like okx_get_spread_orders or okx_get_spread_orders_history. No context on filtering or alternatives.

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