ls_list_files

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds value by detailing pagination behavior (meta.page fields) and cross-store restrictions (variantId requirement under LEMONSQUEEZY_ALLOWED_STORE_IDS). 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?

Three sentences: core purpose, pagination behavior, cross-store nuance. Front-loaded with main action. The third sentence is dense but informative. Could be slightly more concise, but overall efficient.

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 main functionality, optional filtering, pagination details, and an important cross-store constraint. No output schema exists, but the description explains response structure for pagination. Missing details about file object fields, but acceptable given standard list patterns.

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 parameter descriptions. The description adds semantic value beyond schema by explaining the conditional requirement of variantId in cross-store mode and the pagination tie to pageNumber/pageSize. This provides context the schema alone lacks.

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 files' with an optional filter by variant. This is a specific verb-resource pair that distinguishes it from sibling tools that list other entities (e.g., customers, licenses, orders). No ambiguity.

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?

Provides context about pagination and cross-store enforcement but lacks explicit guidance on when to use this tool vs. alternatives. Among many 'list' siblings, the description does not compare or provide when-not-to-use scenarios. It implies use for files, but no clear differentiation beyond resource name.

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