ls_list_order_items

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

The description adds significant behavioral context beyond annotations: it explains pagination (check meta.page for currentPage, lastPage, total) and cross-store filtering constraints. Annotations already indicate read-only, idempotent, non-destructive; description complements them well without contradiction.

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 with three sentences, each adding distinct value: listing function, pagination behavior, and cross-store nuance. No filler or redundancy.

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 100% schema coverage and annotations present, the description covers pagination and cross-store behavior adequately. Could be improved by mentioning typical return fields beyond pagination, but overall sufficient for a list 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 coverage is 100%, so baseline is 3. The description adds value by explaining the cross-store requirement that at least one of orderId, productId, or variantId is needed when LEMONSQUEEZY_ALLOWED_STORE_IDS is set, providing context beyond the schema's basic descriptions.

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 all order items with optional filters by order or product. It distinguishes from sibling tools like ls_get_order_item (single item) and other list tools by specifying the resource and filtering options.

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 guidance on pagination and cross-store filtering requirements when LEMONSQUEEZY_ALLOWED_STORE_IDS is set, but does not explicitly contrast with siblings like ls_list_orders or ls_get_order_item, which would further clarify when to use this tool.

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