List order items

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that results are paginated, which is genuine behavioral context beyond the annotations, but it stops there - no pagination mechanics, default page size behavior, or result shape.

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?

A single short sentence with no padding and no repetition. It is efficient, though the brevity reflects under-specification rather than tight editing of a richer description.

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 7-parameter tool with no output schema and no required fields, the description omits essential context: what an order item is, how the filter parameters combine, whether pagination requires an explicit page cursor, and how this differs from list_orders. The schema plus annotations do not fully compensate for these 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 description coverage is 86%, so the schema already documents page, per_page, account, include, order_id, product_id, and variant_id with meaningful detail. The description adds nothing about parameter syntax or filtering semantics, so the baseline 3 applies.

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 verb and resource (list order items) and mentions pagination, but it reads almost as a restatement of the title and adds no differentiation from closely related siblings like list_orders, get_order_item, or list_subscription_items. An agent cannot tell from this text why it would pick this tool over those.

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?

There is no guidance on when to use this tool versus list_orders or get_order_item, and no mention of the filtering parameters (order_id, product_id, variant_id) that define its actual use case. The agent is left to infer usage from the schema alone.

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