list_stores

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It implies a read-only listing and mentions an optional filter, but it does not explain how filtering behaves, whether results are paginated, what fields are returned, or whether the retailer value is required. The output schema may cover return shape, but the description adds little behavioral context.

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 sentence with no filler, and the core action is front-loaded. However, the conciseness comes at the expense of necessary detail about the query filter and usage context, so it is under-specified rather than efficiently complete.

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 only two parameters, an output schema, and a simple listing operation, the tool is not highly complex. Still, the vague query semantics and lack of usage guidance leave noticeable gaps for an agent deciding how to invoke it correctly. It is minimally viable but not complete.

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 for parameter meaning. It adds only 'with optional query filter,' which gives minimal meaning to 'query' without saying what it filters on (name, location, etc.). The 'retailer' parameter is not explained, though its enum values are self-explanatory.

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 states a clear verb and resource: 'List physical stores for a retailer.' This distinguishes it from the sibling product/stock/price tools at a basic level. However, the 'optional query filter' is vague about what the query targets, which keeps it from being fully precise.

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?

There is no guidance about when to use this tool versus alternatives, and no exclusions or preconditions. The sibling names imply it is for store lookups rather than product searches, but that is left to inference rather than stated.

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