ncloud_get_member_server_image_list

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

The readOnlyHint annotation already declares this as a safe read operation, and the description's 'List' verb aligns with that. Beyond that, no additional behavioral traits (e.g., pagination, default scope, or return format) are disclosed, but the description does usefully define 'member server images'.

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, well-structured sentence that includes the core action, resource, and a clarifying definition. No extraneous words or repetition.

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 simple list operation with one optional filter parameter, the description sufficiently explains the tool's purpose and resource type. Given the readOnlyHint and schema's param description, the lack of output details is acceptable, though it could have mentioned that omitting the parameter returns all member server images.

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 schema description covers the only parameter ('Filter by member server image instance numbers') with 100% coverage, so the description does not need to explain it further. The tool description itself adds no parameter-related information, which is fine given the schema's clarity.

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 identifies the exact resource 'member server images', with a clarifying parenthetical explaining they are 'custom images created from running servers'. This clearly distinguishes it from sibling tools like ncloud_get_member_server_image_detail or ncloud_create_member_server_image.

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 gives contextual info about what member server images are, which implies when this tool is relevant (listing custom images), but does not explicitly state when to use this over alternatives like ncloud_get_member_server_image_detail or how filtering via the parameter works. No exclusions or alternatives are named.

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