get_open_orders

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

With no annotations provided, the description carries the full burden. It does disclose that results are limited to the authenticated account and to active orders only, which is useful behavioral context, but it says nothing about pagination limits, ordering, rate limits, or auth/permission requirements for a listing endpoint that may return many records.

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 purpose is front-loaded in a single clear sentence and the Args block is compact. There is mild redundancy in 'comprehensive list of all open/pending limit orders currently active', but nothing is wasted to the point of harm.

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?

An output schema exists, so return values needn't be explained. For a low-complexity read tool with two optional parameters, the description covers purpose, scope, and both filter parameters; the only real gap is pagination/volume behavior, which is minor here.

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, and it does document both parameters with domain-specific meaning ('market condition ID' and 'CLOB token ID') rather than bare types. The phrasing 'filter results chronologically by market condition ID' is slightly muddled, keeping it from a 5.

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?

States a specific verb and resource ('Retrieve ... open/pending limit orders') scoped to 'the authenticated account', which is enough to distinguish it from siblings like get_order (single order), get_trade_history, and get_positions. It does not explicitly name an alternative tool, so it falls short of a 5.

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?

There is no when-to-use guidance, no statement of when not to use it, and no mention of sibling alternatives such as get_order or cancel_all_orders. Usage must be inferred entirely from the purpose sentence.

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