Get orders

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the sort order and the enumerated status values, but leaves 'recent' undefined — no count, window, or truncation behavior — which matters for a read tool returning a list.

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?

A single clause, front-loaded with the resource and ordering, with zero filler. Nothing redundant relative to the schema or annotations.

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?

There is no output schema, so the description is the only source for return semantics; it covers fields and statuses but not how many orders are returned or how 'recent' is bounded. Adequate for a no-parameter reader, but the result-set size gap is a real omission.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It correctly signals the tool takes no filters, which implicitly tells the agent it cannot scope by instrument or date.

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 concrete resource (orders) and its ordering (newest first) plus the status domain, which distinguishes it from mutation siblings like place_order and cancel_order. It never explicitly names a sibling or says 'retrieves order history', but the returned content is unambiguous.

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 call this versus preview_order or the other read siblings, and no exclusions or prerequisites. Usage is only implied by the description of returned data.

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