List open spot orders

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

Since no annotations are provided, the description carries full behavioral burden. It discloses that the tool is paper trading only with virtual funds and disclaims financial advice, which is helpful. However, it does not mention any potential side effects or data persistence, but given the read-only nature, this is acceptable.

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 two sentences, no fluff. Front-loaded with the core action, followed by required parameter and context (paper trading). Every sentence is essential.

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 list tool with complete parameter schema, the description sufficiently covers purpose, requirement, and environment. Absence of output schema is noted, but the description does not need to detail return format beyond what is implied by 'list open orders'.

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 coverage is 100% with descriptions for both parameters (coinId and limit). The description adds that coinId is required but does not provide additional context beyond the schema. Baseline 3 is appropriate as the schema already documents parameter meaning.

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 'List open (resting) spot orders for ONE coin' with required coinId, which precisely defines the tool's action and scope. It distinguishes from siblings like cancel_spot_order or place_spot_order by focusing on listing.

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 states that coinId is required and notes paper trading only, but does not provide explicit when-to-use or when-not-to-use guidance relative to other sibling tools. The context of 'spot orders' vs futures is implied but not elaborated.

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