find_stores_using_app

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

With no annotations, the description must disclose behavioral traits. It mentions pagination up to 100 per page and that it returns a 'basic profile' for downstream filtering. However, it does not specify authentication requirements, rate limits, or whether the results are limited to the user's accessible stores.

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 concise: two purpose sentences followed by a structured Args block. It is front-loaded with the main purpose. The Args section could be more formally structured (e.g., a list), but it is clear and 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?

Given that an output schema exists, the description does not need to detail return values, but it mentions the 'basic profile' includes store tier/country/industry. It covers pagination and parameter details. Missing details like ordering and exact output fields are compensated by the output schema.

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 0%, so the description must compensate. It explains 'app_slug' as a catalog slug with examples, 'limit' as results per page (1-100), and 'offset' as pagination offset. It also tells how to get slugs via 'list_apps()'. This adds significant value beyond the bare 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 begins with a clear verb and resource: 'List analyzed Shopify stores that have a specific app installed.' This distinguishes it from siblings like 'list_apps' (lists apps) and 'analyze_store' (deep dive on a single store).

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 gives concrete usage examples ('find me stores running Klaviyo') and references 'list_apps()' for obtaining app slugs. It implies when to use (prospecting) but does not explicitly state when not to use it (e.g., for detailed store analysis).

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