ncloud_get_server_images

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

The readOnlyHint annotation already signals a safe read operation. The description adds a constraint about supported hypervisor types, but does not disclose pagination behavior, default result size, or response structure. It is consistent with annotations but adds minimal extra behavioral context.

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 states the core action and includes a useful parenthetical scope note. Every word earns its place with no redundancy.

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?

The tool has 11 optional parameters and no output schema, yet the description does not mention pagination, filter options, or that all parameters are optional. The Gen2/Gen3 note provides some scope context, but the description remains brief for a list operation with this many filters.

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%, so all 11 parameters carry their own descriptions. The tool description does not add any extra parameter semantics beyond what is already in the schema, making the baseline score 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 uses a specific verb ('List') and resource ('server images'), and adds a scope note about Gen2 XEN and Gen3 KVM support. It is clear, though it doesn't explicitly call out distinctions from sibling tools like ncloud_nks_get_server_images or ncloud_ses_get_cluster_server_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?

No guidance is provided on when to use this tool versus alternatives or service-specific image listing tools. The description simply states the function without context, prerequisites, or exclusions.

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