get_orders

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds that a symbol can carry multiple order records in different states, and to check status before describing as open. This goes beyond annotations with useful behavioral context about the return data.

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 short sentences front-load the purpose and practical guidance; every sentence adds value without unnecessary fluff.

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?

With an output schema present, the description covers the main purpose, status interpretation, and filtering. It omits timezone details for 'today' but is sufficient for a simple read-only tool.

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 0%, so the description must compensate. It explains `pending_only=True` filters to working orders, and implies `symbol` filters by symbol ('A symbol usually carries...'). However, it doesn't explicitly state the parameters' optionality or defaults, so compensation is partial.

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 'Get orders placed today with their state' — a specific verb and resource with a timeframe, and enumerates example states. This distinguishes it from sibling tools like get_positions or get_portfolio_overview by focusing on orders.

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?

It provides clear context: the tool retrieves today's orders and advises reading the `status` field before interpreting, plus using `pending_only=True` for working orders. However, it doesn't explicitly compare with alternative tools, so no exclusions are stated.

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