ncloud_ses_get_cluster_server_images

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds the G3/KVM scope constraint, but it does not disclose return format, pagination, or any other behavioral details. Given the annotation coverage, the added context is minimal but not misleading.

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, front-loaded sentence that conveys the essential purpose and constraint with no wasted words. It is appropriately sized for a zero-parameter 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?

Given the tool's simplicity (no parameters, no output schema, read-only annotation), the description sufficiently covers its purpose and scope. It could optionally mention the return value shape, but for a straightforward list operation the current description is adequate.

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 tool has zero parameters, and the schema description coverage is 100% trivially. The baseline for no parameters is 4, and the description's scope mention ('G3/KVM only') adds no parameter-specific meaning but is unnecessary since there are no parameters to document.

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'), the resource ('available OS types'), and the service ('Search Engine Service'), with a specific constraint ('G3/KVM only'). This distinguishes it from related sibling tools like ncloud_ses_get_os_products, which likely covers other generations.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The 'G3/KVM only' qualifier implies a use case, but there is no mention of alternative tools for other generations or any contextual prerequisites, leaving the agent without clear direction among the many SES and CDSS sibling tools.

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