list_customer_groups

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the two underlying API endpoints (GET /customer_groups and /search) and the return structure, which provides meaningful transparency. It does not mention pagination limits or error behavior, but the disclosed info is substantial.

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 well-organized with sections for purpose, API calls, and return structure. The main summary sentence is front-loaded, and every section earns its place without redundancy.

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?

As a simple list tool with no output schema, the description fully compensates by explaining the return structure (total_found, returned, groups[]) and the group fields. It also covers use cases and API behavior, making it complete for an agent to invoke correctly.

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 coverage is 100% for both parameters, so the baseline is 3. The description adds value by clarifying that search_keyword determines which API is called (search endpoint vs. list endpoint), giving behavioral context beyond the schema's simple field descriptions.

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: '取得客戶群組列表，支援依名稱搜尋' (Get customer group list, supports searching by name). It distinguishes itself from sibling tools like get_customer_group_members by noting it provides group IDs for further member queries.

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 '【用途】' section explains when to use the tool (browse/search groups, confirm segmentation strategy, get group ID for member lookup). It implies a workflow but does not explicitly name alternatives or state when not to use it.

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