ls_list_discount_redemptions

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds valuable behavioral details: pagination metadata (meta.page with currentPage, lastPage, total) and cross-store enforcement nuances. No contradictions with annotations.

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 plus a note, all front-loaded with the core purpose. Every sentence provides essential information: action, filters, pagination, and cross-store considerations. No extraneous words.

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 list tool with no output schema, the description covers pagination response structure and filtering constraints. It addresses an edge case (cross-store environment). Could mention default pagination or record shape, but the current text is sufficient for effective use.

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% with each parameter having a description. The description adds cross-store filtering context tied to discountId and orderId, and pagination guidance for pageNumber/pageSize. It explains the meta.page structure beyond 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 action ('List'), resource ('discount redemptions'), and optional filters ('by discount or order'). It distinguishes itself from sibling list tools (e.g., ls_list_discounts, ls_list_orders) by specifying the exact resource type.

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 context about cross-store filtering requirements and the need for a scoped API key. It explains when filters are required (when LEMONSQUEEZY_ALLOWED_STORE_IDS is set). It does not explicitly contrast with sibling tools but gives clear conditions for use.

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