List customer groups

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

The description is minimal, using 'Fetch' to imply a read operation, but with no annotations, it does not disclose other behavioral aspects such as authentication, side effects, or pagination behavior beyond what the schema indicates. It is not misleading but lacks depth.

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, front-loaded sentence without filler words. It efficiently communicates the tool's purpose with no waste.

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 is mostly adequate. It clearly states what is fetched and the schema covers pagination parameters. However, since there is no output schema, the description could provide a bit more detail on the return format, but it does not severely hinder comprehension.

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 both page and pageSize, so the tool description does not need to add parameter semantics. The description adds no extra value beyond referring to 'a page', which is already covered in the schema, so baseline 3 is appropriate.

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's function with the verb 'Fetch' and the resource 'customer groups', distinguishing it from sibling tools like list_customers and get_customer. It precisely indicates a paginated read 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 implies usage for listing customer groups, but it does not provide explicit guidance on when to use this tool versus alternatives. There is no mention of exclusions or preferred scenarios compared to other list tools.

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