ncloud_cdss_get_cluster_acg

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

The description simply restates the tool name with no additional behavioral context. The readOnlyHint annotation is present, but the description adds no extra information about pagination, return format, or permission requirements beyond what the annotation already implies.

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, concise sentence that is front-loaded and contains no unnecessary words. It efficiently communicates the core function.

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 getter with no output schema, the description is minimal and does not explain what the response contains, what ACG rules are, or any relevant details. The presence of a readOnlyHint annotation helps somewhat, but the description does not fully cover the context needed for an agent to understand the tool's behavior.

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 fully documents the single parameter serviceGroupInstanceNo with a description 'Cluster instance number', giving 100% schema coverage. The tool description adds no additional meaning or context about the parameter, so the baseline score of 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 verb 'Get' and the resource 'ACG rules for a CDSS cluster', which is specific and unambiguous. It distinguishes from similar tools like ncloud_ses_get_cluster_acg by explicitly scoping to CDSS clusters, though it does not explicitly mention alternatives.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no context about cluster access or configuration. The description only states what it does, leaving the agent to infer usage.

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