ncloud_nks_get_server_images

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

The readOnlyHint annotation already indicates a safe read operation, and the description's 'List' aligns with that. The description adds the context that images are for NKS cluster/node pool creation but does not disclose additional behaviors such as response format or default hypervisorCode (which is in the schema). No contradiction found.

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 sentence, front-loaded with the action verb 'List', and contains no unnecessary filler. It earns its place by clearly stating the resource and purpose.

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?

This is a simple tool with one optional parameter and a readOnly annotation. The description clearly states what it lists and for what purpose. Since there is no output schema, the description could be more explicit about the response structure, but 'server image types' is sufficiently clear for this low-complexity operation.

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 sole parameter hypervisorCode. The tool description adds no extra parameter semantics beyond what the schema already provides, so the baseline score 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 uses a specific verb ('List'), a specific resource ('available server image types'), and a clear context ('for NKS cluster/node pool creation'). This distinguishes it from sibling tools like ncloud_get_server_images (general server images) and ncloud_nks_get_server_specs (server specs, not images).

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 implies usage for NKS cluster/node pool creation, which gives clear context. However, it does not explicitly state when not to use this tool or name alternative tools (e.g., ncloud_get_server_images for non-NKS scenarios), so guidance is only implied.

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