get_orders

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

Adds substantial behavioral details beyond annotations: date format KST, order time, limit default/max, cursor/limit only for CLOSED, and OPEN returns all. No contradiction with readOnlyHint.

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 concise sentences pack significant information; front-loaded with the primary action and status grouping.

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 an output schema exists, the description doesn't need return details. It covers the key usage behaviors: status, date filtering, and pagination asymmetry between OPEN and CLOSED. Very complete for a list 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?

With 0% schema description coverage, the description compensates by explaining status, date range, limit/cursor semantics. However, symbol and account_seq are left unexplained, though they are optional and reasonably inferable from names.

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 states the tool 'List orders by lifecycle group' and defines the status values, clearly identifying the resource and scope. It is distinguishable from sibling tools like get_order which retrieves a single order.

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?

Provides clear context: date range format, KST, order time, and explicit pagination behavior for CLOSED vs OPEN. Does not explicitly name alternative tools for single-order lookup, but the usage parameters are well-defined.

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