ncloud_create_member_server_image

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

The annotations already set destructiveHint=false, so the description adds minimal behavioral context beyond noting the source server must be running. It does not disclose side effects (e.g., whether the server continues operating), required permissions, or error scenarios, but with annotations covering the safety profile, the gap is moderate.

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 conveys the essential purpose without unnecessary words. It is optimally front-loaded and 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?

The tool has no output schema and the description does not mention return values or expected behavior (e.g., asynchronous operation). For a creation tool, this is a notable gap, but given the simplicity and full schema coverage, it is minimally adequate.

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 100% parameter description coverage, so the description adds no additional meaning. Baseline score of 3 is appropriate as the schema already documents the parameter semantics.

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 action (create) and the resource (member server image) and specifies the source (from a running server instance). This distinguishes it from sibling tools like ncloud_create_server_image (likely from a different source) and ncloud_create_server_image_from_snapshot.

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 the server must be running but does not explicitly state when to use this tool versus alternatives (e.g., ncloud_create_server_image_from_snapshot). No prerequisites, constraints, or when-not-to-use information is provided, leaving the agent to infer usage from the name only.

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