ls_list_discount_redemptions

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

Beyond annotations (readOnlyHint, etc.), the description adds important behavioral context: pagination (check meta.page), security requirements when store filtering is active, and that the API key's visibility is the true boundary. No contradiction 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?

Four sentences, front-loaded with main purpose, each sentence adds distinct value: purpose, pagination, cross-store security, and API key guidance. No redundant text.

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?

Covers purpose, filtering, pagination, and security nuances. Without output schema, it still provides enough context for agent understanding. Missing explicit mention of return format, but pagination hint compensates.

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%, baseline 3. Description adds value by linking pagination to parameters (discountId, orderId) and hinting at response structure (meta.page), going beyond schema 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 discount redemptions with optional filters, using the verb 'List' and specifying the resource. It distinguishes itself from siblings like ls_get_discount_redemption and other list tools.

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?

Explicitly states when to use with optional filters and provides a crucial cross-store security note: when LEMONSQUEEZY_ALLOWED_STORE_IDS is set, either discountId or orderId is required, and advises using a scoped API key for true enforcement.

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