list_orders

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not state account scoping, ordering, pagination, or whether 'all' means all accounts or all orders within the default account.

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 a single front-loaded sentence with no filler words, which is concise. It sacrifices needed semantic detail but remains appropriately terse for such a simple operation.

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?

While an output schema exists to document return values, the description still leaves critical invocation context missing: no account semantics, no mention of the optional parameter, and no relationship to sibling order-management tools. For a tool with one optional parameter, this is below minimum viable completeness.

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%, and the description does not compensate by explaining the 'account' parameter. In fact, saying 'all pending limit orders' while exposing an account parameter creates ambiguity: an agent cannot tell whether the account parameter filters the list or whether 'all' is truly global.

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 a specific verb ('List') with a clear resource and scope: 'all pending limit orders.' This is unambiguous about what the tool does. However, it does not explicitly differentiate itself from sibling tools like check_orders, which could plausibly overlap.

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 provides no guidance on when to use this tool instead of alternatives. It does not mention check_orders, cancel_all_orders, or any other sibling as a comparison, leaving the agent to infer placement entirely from the name.

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