cigchat_list_products

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

No annotations are provided, so the description carries the transparency burden. It discloses the auth requirement and the GET method, indicating a read operation, but it does not describe the return format, pagination behavior, or default limits. This is a minimal but not comprehensive disclosure.

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 that immediately states the purpose and ends with the auth scope. There is no redundant information, making it highly concise and front-loaded.

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?

The tool has no annotations, no output schema, and the description provides minimal context. It fails to explain what the response looks like, whether pagination is handled, or any defaults for page/limit. Given the complexity of multiple optional filters, the description is insufficient for an agent to confidently invoke the tool without additional assumptions.

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 all five parameters, so the baseline is 3. The description adds no parameter-specific details beyond what the schema already provides, and it does not mention filtering or pagination semantics.

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 uses the specific verb 'Get' with a clear resource 'list of products' and even includes the API endpoint '[GET /shop/products]'. It clearly distinguishes from sibling tools like list_tags or list_product_types by focusing on products, and from shop_products_get_info by being a list operation.

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 gives the prerequisite of the 'Manage Team' scope but does not explicitly state when to prefer this tool over alternatives such as shop_products_get_info or list_product_vendors. The use case is implied—listing products—without exclusions or alternative guidance, so it remains at an implied level.

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