getOrderHistory

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

Discloses key behaviors: 2-year data limit, 7-day max span, default period, pagination via cursor, and filter options. No annotations provided, so description carries full burden; lacks mention of rate limits or response format but sufficient for safe read operation.

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?

Concise, well-structured with bullet points and agent hint. Every sentence adds value, no fluff. 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?

Given 12 parameters, no annotations, and no output schema, the description covers purpose, usage, key filters, and sibling distinction. Missing details on some parameters (symbol, coin) and return format, but overall sufficient for an agent to select and invoke correctly.

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?

With 0% schema description coverage, the description adds meaning for critical parameters: startTime/endTime (limits), cursor (pagination), orderFilter (type filter), orderStatus (status filter), category (TradFi mapping). Does not cover symbol, baseCoin, etc., but these are inferable from names. Adds significant value over schema.

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 the tool queries historical order records, specifying verb and resource. It differentiates from siblings like getOpenOrders via the agent hint, and provides context like TradFi category mapping.

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?

Explicit guidance on when to use (completed/cancelled/expired orders) and when not (active orders, recommending getOpenOrders). Includes max time span, pagination, and filter usage.

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