list_orders

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

No annotations provided, so description must disclose behavior. It mentions status filter but omits pagination behavior (limit/cursor only for CLOSED), sorting, or read-only nature (likely safe, but not stated). This leaves gaps for the agent.

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 clear sentences, no redundancy. Every word is useful. Front-loaded with the core action.

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 7 parameters, required status, and no output schema/annotations, the description is too brief. It misses pagination specifics, return structure, and behavioral differences between OPEN and CLOSED (cursor/limit). Incomplete for tool complexity.

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 100% with detailed param descriptions. The description adds value by explaining status enum values (OPEN=in progress, CLOSED=completed/cancelled), but does not enhance understanding of other params like from, to, limit, cursor, symbol, accountSeq beyond the 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 'query order list' and defines the status parameter values (OPEN and CLOSED) with Korean explanations. It distinguishes from siblings like get_order (single order) and list_conditional_orders (conditional orders), but could explicitly differentiate between these.

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 use this tool vs alternatives like get_order, list_conditional_orders, or when not to use it. The description only states what it does without context for choosing this over siblings.

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