ncloud_get_member_server_image_detail

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

The description aligns with the `readOnlyHint: true` annotation by stating 'Get detailed information', but adds no additional behavioral context beyond what annotations provide. No mention of error handling, response structure, or side effects.

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 short sentence with no extraneous words. It could be slightly more informative (e.g., hinting at return fields) but remains efficient.

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 (1 param, no output schema), the description is minimally viable. However, it lacks details on what 'detailed information' includes, which would help agents understand the return value without an output schema.

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 coverage is 100%, and the parameter description in the schema ('Member server image instance number to query') is clear. The tool description does not add further semantics (e.g., format, constraints) beyond the schema.

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 'Get' and identifies the resource as 'detailed information about a member server image instance'. It clearly distinguishes from sibling tools like `ncloud_get_member_server_image_list` (which lists all images) and `ncloud_get_server_image_detail` (which retrieves server image details instead of member 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?

The description provides no guidance on when to use this tool versus alternatives such as `ncloud_get_member_server_image_list` or `ncloud_get_server_image_detail`. It does not mention prerequisites (e.g., having an instance number) or context for selection.

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