ls_list_prices

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds value by detailing pagination (meta.page fields) and the cross-store configuration note, which discloses important behavioral context not covered by 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 front-loaded with the core purpose, followed by pagination details, and then a cross-store note. It is moderately concise; the cross-store note is slightly verbose but important. No wasted sentences.

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 no output schema, the description covers pagination and variant filtering well. It explains a key cross-store configuration scenario. However, it does not describe the response structure beyond pagination fields (e.g., that it returns an array of price objects), which would be helpful.

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?

Input schema has 100% coverage with descriptions, so baseline is 3. The description adds that the variantId filter is optional and, crucially, that it becomes required when LEMONSQUEEZY_ALLOWED_STORE_IDS is set, providing extra semantic context 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 'List all prices' with optional variant filtering, which is a specific verb+resource combination. It clearly distinguishes from sibling list tools (e.g., ls_list_products, ls_list_variants) by focusing on prices, and from ls_get_price which retrieves a single price.

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 clear context: it lists prices optionally filtered by variant, and includes a cross-store note about configuration requirements. However, it does not explicitly state when NOT to use this tool (e.g., when a single price is needed) or mention alternatives, though siblings are available.

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