Search Orders

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

Disclosures beyond annotations include temporal scope (data since 2026-01-26), pagination behavior, file dumping with outputPath, and the absence of rejected orders. No contradiction with annotations.

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?

Extremely concise: two sentences plus a parenthetical, each sentence provides essential information. Front-loaded with core purpose.

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?

Despite 7 parameters and no output schema, the description covers all key aspects: data returned, filtering, pagination, file dumping, and limitations. No gaps.

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?

Adds significant meaning beyond schema: explains that page is ignored with outputPath, that outputFormat defaults based on file extension, and describes outputPath behavior with a concrete response structure example.

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 that the tool lists orders with specific fields (ticker, side, type, etc.) and includes a data range. It distinguishes from sibling tool get_order_status by noting that rejected orders are not shown here.

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?

Explicitly tells when to use (to get orders) and when not to (rejected orders), providing the alternative tool get_order_status. Also explains use of outputPath for bulk data.

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