Retrieve the list of CDSS clusters associated with a config group to verify dependencies before deletion.
List the CDSS clusters a Config Group is currently applied to. Call this before deleting a group.
| Name | Required | Description | Default |
|---|---|---|---|
| pageNo | No | Page number (default: 1) | |
| pageSize | No | Page size (default: 10) | |
| configGroupNo | Yes | Config group number (from ncloud_cdss_list_config_groups) |
Changes observed during successful MCP inspections.
v1.15.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates safety. The description adds limited behavioral context by noting the clusters are 'currently applied to' and positioning the call before deletion, but it does not disclose response shape or pagination behavior. This is adequate but not rich.
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?
Two tightly written sentences with no filler. The primary purpose is front-loaded, and the usage directive is a compact second sentence that earns its place by advising when to call the tool.
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 with one required parameter and two pagination fields already documented in the schema, the description is sufficient. It lacks explicit return-format details and there is no output schema, but the purpose and workflow context are clear enough for an agent to invoke it 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 description coverage is 100%, so the schema already documents all three parameters, including that configGroupNo comes from ncloud_cdss_list_config_groups. The description adds no supplementary parameter meaning beyond what the schema provides, so the baseline of 3 applies.
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 states a specific verb ('List') and resource ('CDSS clusters a Config Group is currently applied to'), making the tool's scope unmistakable. It differentiates from the related ncloud_cdss_list_clusters and ncloud_cdss_delete_config_group by clarifying this is a cluster-to-config-group association query.
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 sentence 'Call this before deleting a group' gives explicit workflow context and signals this tool is a pre-deletion check. It does not enumerate alternatives or state when not to use it, so it stops short of full exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.