ls_list_stores

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

No annotations exist to disclose safety or side effects. The description does not mention authentication requirements beyond the api_key parameter, rate limits, pagination behavior, or what the return value contains. The lack of behavioral detail for a read operation is a notable gap.

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 a single concise sentence with no extraneous content. However, its brevity sacrifices essential details such as pagination or output format, making it borderline under-specified.

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 the tool has 3 parameters, no output schema, and no annotations, the description is too brief. It fails to explain pagination, required inputs beyond api_key, or the response structure. A more complete description would cover these aspects.

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 only 33% (only api_key has a description). The description does not explain the purpose of 'page' or 'per_page', leaving their semantics ambiguous. The description adds no parameter value 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 tool lists all Lemon Squeezy stores on the user's account. The verb 'List' and resource 'stores' are unambiguous, and it differentiates from other ls_* tools that handle orders, customers, products, and subscriptions.

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?

No guidance is provided on when to use this tool versus alternatives like ls_list_customers or ls_list_products. There is no mention of prerequisites, limitations, or scenarios that would make this tool inappropriate.

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