ncloud_ses_get_cluster_server_images

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

The description adds the constraint '(G3/KVM only)' beyond the readOnlyHint annotation, which is useful. However, it does not disclose other behavioral traits like whether it returns a list, pagination, or caching behavior. Since annotations already indicate read-only, the description provides moderate additional value.

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 of 12 words, no filler, clearly front-loads the purpose. Every word earns its place, achieving maximum conciseness.

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 read-only tool with no parameters and no output schema, the description is mostly complete: it specifies the service (Search Engine Service), the environment (G3/KVM only), and the action (get available OS types). Minor gaps: does not describe the output format or that no input is required, but these are easily inferred.

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, so there is nothing to describe. The description adds no parameter-specific information, but the baseline for 0 parameters is 4. The tool's purpose is sufficiently conveyed without parameter details.

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 retrieves available OS types specifically for Search Engine Service, limited to G3/KVM only. The verb 'Get' and resource 'available OS types' are specific, and the scope distinguishes it from sibling tools like ncloud_ses_get_node_products or ncloud_ses_get_server_specs.

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 on when to use this tool versus alternatives. While the description mentions the service and environment, it does not provide context such as prerequisites, when to prefer this over other SES tools or general server image tools.

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