order_list

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

With no annotations present, the description does not disclose behavioral traits such as that it is a read operation, whether results are paginated (though page/limit params suggest it), or any defaults or side effects. It only lists parameter meanings.

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?

The description is a clean, bullet-like list of parameters with clear one-line explanations. No extraneous information; every sentence earns its place.

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 the presence of an output schema (not shown but indicated), the description adequately covers the input parameters. It does not describe the return format or behavior, but the output schema presumably covers that. The parameter descriptions are sufficiently complete for a listing 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 description coverage is 0%, so the description fully compensates by explaining each parameter's purpose (e.g., 'Filter by internal order ID'). It also specifies date format (YYYY-MM-DD) and limit range (1–100), adding value beyond the schema's titles.

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 'List orders from the Gomag store,' identifying the verb 'list' and resource 'orders.' This distinguishes it from sibling tools like 'order_create' or 'order_status_types,' though it does not explicitly contrast with them.

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 is provided on when to use this tool versus alternatives (e.g., 'order_status_types' for status keys, 'order_create' for creation). No prerequisites or context for usage are mentioned.

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