List Orders

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

The description aligns with annotations (readOnlyHint, openWorldHint) and adds that the tool returns orders with items, shipping details, and status. No contradictions or negative behaviors disclosed, which is appropriate given the read-only nature.

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 concise at four sentences, front-loading the purpose and then explaining filters. Every sentence adds value, and there is no fluff.

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?

While the description covers key filters, it omits mention of pagination (page parameter), changeIntervalMinute, latestChangeDate, and vvbOnly. Given the schema provides descriptions, the description is adequate but could be more complete for a tool with 6 optional parameters.

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 100%, and the description adds context for the fulfilmentMethod and status parameters by explaining the enum values (e.g., OPEN means awaiting shipment/cancellation). This adds value beyond the schema alone.

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 lists recent orders from bol.com and returns orders with items, shipping details, and status. It distinguishes from siblings by specifying the resource and scope.

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?

The description provides explicit guidance on using the fulfilmentMethod and status filters, indicating when to use them. However, it does not explicitly mention when not to use this tool or alternatives like get_order for single order details.

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