list_shops

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly signals a read-only, account-scoped enumeration, which is useful, but it does not disclose return format, pagination, ordering, or behavior when no shops exist.

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 one concise sentence with no filler. The key qualifiers ('every shop' and 'authenticated Vendor Center account') are front-loaded and immediately useful.

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 zero-parameter list operation, the description is largely complete: an agent can invoke it without needing further input. The absence of an output schema and any note about the returned shop fields or pagination leaves minor ambiguity, but the tool's low complexity keeps this from being a major gap.

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 input schema has zero parameters and full description coverage, so there is nothing for the description to add about parameter handling. This matches the baseline for no-parameter tools.

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 names a specific verb ('List') and a precise resource ('every shop under the authenticated Vendor Center account'). This clearly separates it from sibling list tools such as list_brands and list_categories, so an agent can identify what it does without opening schemas.

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 intended usage is implied: call this tool when you need the shops belonging to the authenticated account. However, there is no explicit guidance about when not to use it, no mention of alternatives, and no hint about common follow-up steps such as obtaining shop IDs for other operations.

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