ncloud_get_server_images

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

Annotations include readOnlyHint=true, which is consistent with listing. The description adds that it supports Gen2 and Gen3 hypervisors, a behavioral trait not in annotations. However, it does not clarify pagination behavior, filtering semantics beyond schema, or response structure. Minimal added value beyond 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 sentence conveying the core purpose and hypervisor support. It is concise and front-loaded, but could be slightly more informative without losing brevity. No unnecessary words.

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?

Given the large sibling list and lack of output schema, the description is somewhat incomplete. It does not explain that these images are used for server provisioning, nor does it differentiate between public/private or member images. The minimal information suffices but lacks context for an agent to fully understand its role.

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 all 11 parameters. The description adds no additional meaning or constraints beyond what the schema already documents. 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 tool lists available server images and specifies support for Gen2 XEN and Gen3 KVM hypervisors. This differentiates it from sibling tools like ncloud_get_server_image_detail (single image) and ncloud_list_servers (list instances).

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 does not provide guidance on when to use this tool versus alternatives. With many sibling list tools (e.g., ncloud_get_server_image_detail, ncloud_list_servers), explicit usage context is missing. No mention of prerequisites or when not to use.

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