cigchat_list_shop_locations

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

The description discloses the required 'Manage Team' scope and the HTTP method/path, which adds behavioral context beyond the bare tool name. However, it doesn't mention pagination behavior, response format, or any safety implications (e.g., read-only nature). With no annotations, more detail would be expected.

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 concise sentence containing both the purpose and the auth constraint, with no unnecessary words. Each piece of information is useful, though it could benefit from a slightly more structured format.

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 operation, the description covers the basic function and a key requirement, but it omits details like response shape, pagination limits, or whether the list is ordered. The schema helps with parameters, but the lack of an output schema and annotations leaves some gaps.

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 provides full descriptions for all three parameters (name, page, limit), so the description adds no extra meaning. The description doesn't mention any parameter relationships or defaults, but the schema covers semantics sufficiently.

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 retrieves a list of locations, distinguishing it from sibling CRUD operations like create/update/delete/get_info. The endpoint is included, adding specificity. However, it doesn't explicitly clarify the scope (e.g., all locations vs filtered) beyond what the schema parameters imply.

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 cigchat_shop_locations_get_info. The description gives no exclusions or alternative suggestions. The only additional context is the required auth scope, which is a prerequisite, not a usage guideline.

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