getSpreadOrderHistory

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behaviors: closed-only scope, 24-hour retention for fully cancelled orders, exclusion of certain single leg futures spread orders, and precise startTime/endTime range rules. These materially affect how an agent should invoke the tool.

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 compact and well organized: core behavior is front-loaded, and the notes and time-range rules are separated into scannable bullet points. There is no redundant or filler text.

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?

The description is sufficient for making a default 7-day query and understanding the time-window constraints. However, there is no output schema and no description of the return shape, pagination behavior related to cursor, or semantics for the filtering parameters, leaving notable gaps for more advanced use.

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 0%, so the description must compensate for parameter meaning. It thoroughly explains startTime and endTime behavior, but the remaining six parameters (limit, cursor, symbol, orderId, baseCoin, orderLinkId) are not described beyond their schema names.

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 clearly states the operation ('Query spread trading order history') and the resource scope ('spread combination orders'), and specifies that only closed (filled, cancelled, rejected) orders are returned. This distinguishes it from sibling tools like getSpreadOpenOrders and getSpreadTradeHistory.

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 gives a clear routing rule: single leg orders created via futures spread belong to the primary order history endpoint with createType=CreateByFutureSpread. It also explains the time-range selection behavior in detail. However, it does not explicitly name sibling tools such as getSpreadOpenOrders for open-order use cases.

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