Order items

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

No annotations are provided, so the description must carry the full burden. It explicitly states the tool is read-only ('without adding anything'), which is a key behavioral trait. It does not disclose other details like authentication requirements or return format, but for a simple read tool, this is relatively transparent.

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 two sentences, no wasted words, and front-loaded with the main action. Every sentence adds value: first states purpose, second adds default behavior and modifies guidance.

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?

For a simple tool with one optional parameter and no output schema, the description adequately covers purpose, default behavior, and non-destructive nature. It could mention that the response is a list of items, but the sibling context (get_product, search_products) helps fill gaps.

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% (only one parameter). The parameter description in the schema ('Order id from get_purchase_history; default = latest order') is sufficient. The main description reinforces the default behavior, adding extra context over 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 the tool lists products in a past order, with the verb 'List' and resource 'products in a past order'. It distinguishes from modifying siblings like add_to_cart and reorder_order by noting 'without adding anything', and implies it is for past orders, not the current cart (get_cart).

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 does not explicitly state when to use this tool versus alternatives like get_cart (for current cart) or get_purchase_history (for order list). It implicitly suggests use for past orders and defaults to most recent, but lacks clear when/not guidance.

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