ncloud_get_server_image_detail

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

The readOnlyHint annotation already declares this as a safe read operation, so the description's addition of 'detailed information' and 'specific' provides minimal extra behavioral context. It does not disclose response format, error behavior, or field details, but given the annotation and the simplicity of the operation, this is acceptable.

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 concise sentence that is front-loaded with the action and resource. Every word contributes to the meaning, with no redundant phrasing or unnecessary detail.

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 simple one-parameter input, the presence of readOnlyHint, and the clear subject matter, the description is mostly complete. The absence of an output schema means the description could have specified what 'detailed information' includes, but the phrase 'detailed information about a specific server image' is sufficient for an agent to understand the tool's purpose and select it appropriately.

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% with the sole parameter 'serverImageNo' described as 'Server image number to query' in the schema itself. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

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 'Get detailed information about a specific server image' uses a specific verb ('get'), a clear resource ('server image'), and scope ('specific'), which accurately distinguishes it from sibling list tools like ncloud_get_server_images. Although it doesn't explicitly mention alternative detail tools, the name and description unambiguously identify the operation.

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 implies usage when you need details for an individual image, but it provides no explicit guidance on when to use this tool versus alternatives such as ncloud_get_server_images for listing or ncloud_get_member_server_image_detail for member images. No exclusions or alternative suggestions are given, making the usage context clear but not explicitly articulated.

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