ncloud_cdss_get_cluster_server_images

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

The annotation readOnlyHint=true already establishes this as a safe read operation. The description adds the platform scope (G3/KVM), which is useful context beyond the annotation, but it does not reveal other behavioral aspects such as result format, pagination, or any caveats. It does not contradict 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?

The description is a single, concise sentence that front-loads the key information (what it gets and for which service). There is no redundancy or filler, making it appropriate for a simple read-only 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 zero-parameter, read-only listing tool, the description is largely sufficient. It names the resource and scope. However, without an output schema, it does not indicate what the returned image list contains or how it might be used (e.g., for cluster creation). Slightly more context would improve it, but the simple nature of the tool keeps it from being incomplete.

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 has zero parameters and the description correctly implies no parameters are needed. With no parameters, the baseline is 4; the description adds slight clarity by specifying the service scope (G3/KVM) but not much else. The schema already fully covers the lack of parameters.

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 'Get available OS images for CDSS (G3/KVM)' clearly states the action (get), the resource (OS images), and the scope (CDSS, specifically G3/KVM). This distinguishes it from sibling tools like ncloud_ses_get_cluster_server_images and ncloud_nks_get_server_images by explicitly naming the CDSS service and platform generation.

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 provides no guidance on when to use this tool versus alternatives such as ncloud_cdss_get_os_products or ncloud_cdss_get_server_spec_list. It does not mention prerequisites, context (e.g., cluster creation), or exclusions. The usage is only implied by the name and brief scope.

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