ncloud_cdss_list_config_groups

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered by structured data. The description adds semantic context ('Kafka configuration templates') but no additional behavioral details like pagination, authentication, or response structure. No contradiction with annotations.

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?

Single sentence with clear subject-verb-object structure: 'List Config Groups for CDSS (Kafka configuration templates)'. No wasted words; the parenthetical adds valuable domain context without bloat.

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?

Simple list tool with one optional parameter and a readOnly annotation. Description adequately states what is listed and clarifies the domain. No output schema is present, but for a standard list operation this is sufficient. Could optionally mention that all groups are returned when no filter is provided, but not essential given the tool's simplicity.

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 the single parameter kafkaVersionCode, which is documented as 'Filter by Kafka version code'. The description adds nothing about parameter usage, so the baseline of 3 applies per high schema coverage.

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?

Description uses a specific verb 'List' with resource 'Config Groups for CDSS' and clarifies they are 'Kafka configuration templates'. This clearly distinguishes from sibling tools like ncloud_cdss_get_config_group_detail, which implies a single-item detail view.

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 explicit when-to-use or alternative guidance is provided. The 'List' verb implies use when an overview of config groups is needed, but there is no exclusion or comparison against ncloud_cdss_get_config_group_detail or ncloud_cdss_create_config_group.

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