List stores

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description adds crucial behavioral details: the exact endpoint, the response shape with optional fields, and the fact that status values are not enumerated upstream. This gives the agent a realistic expectation of the output and potential variability.

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, using two sentences to convey scope, response shape, and integration hints. Every sentence adds value, and the front-loaded 'All stores' immediately clarifies the tool's function.

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?

With no output schema, the description fully specifies the return format and key semantics (store id, status). It also accounts for the open-world hint by noting status values are not enumerated, making the tool safely usable despite incomplete API documentation.

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?

The tool has zero parameters, so the baseline is 4. The description reinforces 'no parameters' and explains what the returned store id represents, which is helpful context beyond the empty 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 stores (darkstores) for the retailer, with the verb 'list' appearing in the title. It also distinguishes itself from siblings by noting the store id is used by other tools, making its purpose unambiguous.

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 identifies the endpoint and explicitly states no parameters are required, which signals when to call it. It also notes that the store id is used by create_order, update_stocks, and create_discounts, implying this is the prerequisite tool for those operations. However, it does not explicitly mention exclusions or alternatives, though none exist among siblings.

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