getSpreadOpenOrders

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

With no annotations, the description discloses key behaviors: returns only 'New or PartiallyFilled' orders, supports cursor-based pagination (max 50), may experience latency during high volatility, and is a GET endpoint requiring auth. Adequate transparency for a read query.

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?

Description is concise and well-structured with sections (Usage Scenarios, Important, Agent hint). Bullet points enhance readability. No wasted words; every sentence adds value.

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 6 parameters, no output schema, and no annotations, the description covers purpose, parameter usage, pagination behavior, and latency. Lacks detail on return format, but overall complete for a read tool.

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 fully compensates by explaining the purpose of each parameter: filter by symbol/baseCoin, look up by orderId/orderLinkId, paginate with cursor, limit results. Adds significant meaning beyond the schema's type/constraints.

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 it queries 'real-time open spread trading orders'. It uses specific verbs ('Query') and resources ('open spread trading orders'), and distinguishes from siblings like 'getSpreadOrderHistory' by focusing on current open orders.

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?

Provides explicit usage scenarios (monitor all, filter by symbol/baseCoin, look up by ID, paginate) and notes all parameters are optional. Mentions authentication requirement. Could be more explicit about when not to use (e.g., for historical orders), but sufficient.

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