get_all_orders

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

The description fails to disclose that a status filter is required, that results are limited, or any ordering/pagination behavior. With no annotations, the description carries the full burden but is minimal and slightly inaccurate.

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?

Two sentences, front-loaded with purpose. The second sentence is redundant but not harmful. No unnecessary information.

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 the presence of output schema and two parameters, the description is insufficient. It omits the required status filter, the meaning of the limit parameter, and any details about the output beyond 'a list of 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 description coverage is 0% and the description adds no parameter details. It does not explain the required status parameter or the limit parameter. The schema has descriptions, but the description text fails to compensate for the low coverage.

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 retrieves limit, take profit, and stop loss orders and returns a list. It distinguishes from sibling tools like list_dca_orders. However, the word 'all' is misleading given the limit parameter.

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?

No guidance on when to use this tool versus alternatives like list_dca_orders or search_calls. No mention of prerequisites or context.

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