list_stores

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

The description mentions the returned fields but does not disclose pagination behavior despite limit/offset parameters being present. The word 'all' may mislead an agent into thinking a single call returns everything, and no annotations are available to cover safety or side effects.

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?

A single sentence that is clear, front-loaded with the action, and contains no redundant information. It efficiently states what the tool does and what it returns.

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 simple list tool, the description covers the core purpose and return fields, but the absence of an output schema and lack of mention of pagination leave gaps. The agent would need to infer pagination from the parameters.

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% for both limit and offset, with defaults and constraints fully documented. The description itself adds no parameter-level details, so the baseline of 3 applies.

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 verb 'List' and resource 'warehouses/stores' are specific, and the description clearly states the returned fields (names, addresses, meta hrefs). It distinguishes from sibling search/get tools by implying a complete listing rather than a filtered lookup.

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 search_products or get_stock_by_store. There are no explicit exclusions or preferred use cases.

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