ls_list_license_key_instances

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds beyond these by detailing pagination behavior (meta.page fields) and cross-store enforcement details involving LEMONSQUEEZY_ALLOWED_STORE_IDS and API key scoping.

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, each serving a distinct purpose: purpose, pagination guidance, cross-store note. Front-loaded with the core action. No unnecessary 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 4 parameters and no output schema, the description covers pagination and important cross-store context. It doesn't explain return fields beyond meta.page, but annotations and schema partially compensate. Could mention what a 'license key instance' represents, but overall sufficient.

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 description coverage is 100%, so baseline is 3. The description adds limited parameter context beyond the schema: it mentions optional filtering by licenseKeyId and pagination implicitly. No contradictions or new constraints are introduced except the note about licenseKeyId being required in cross-store mode.

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 verb 'list' and the resource 'license key instances (activations)'. It distinguishes this from sibling tools like ls_get_license_key_instance by implying it returns multiple items, and the term 'instances' differentiates it from ls_list_license_keys.

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 clear context for pagination (check meta.page) and a note about cross-store filtering requirements. While it doesn't explicitly say when not to use this tool versus alternatives, the purpose is clear and the note about requiring licenseKeyId in some setups helps guide usage.

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