ncloud_create_server

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

Annotations only declare destructiveHint=false, so the description carries the burden of behavioral insight. It adds the dryRun preview behavior and the generation-specific parameter requirements, which are significant beyond the annotation. It does not cover return behavior or async execution, but for a creation tool this is adequate.

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?

Three sentences, front-loaded with the main purpose, then compact technical guidance. No redundancy or filler. Every sentence earns its place.

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 17-parameter creation tool with no output schema, the description covers the core creation behavior, generation-specific parameter selection, and dryRun preview. It does not discuss billing, mutual exclusivity of all parameter combinations, or return values, but the critical invocation guidance is present.

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 already has 100% description coverage for parameters, but the description adds crucial relational semantics: which parameter groups are valid together and which generation they apply to. This goes beyond individual field descriptions (e.g., serverImageNo vs serverImageProductCode) and clarifies when to use one set versus another.

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 opens with 'Create a new server instance', a specific verb+resource that clearly distinguishes this from sibling tools like ncloud_terminate_server or ncloud_create_server_image. It further clarifies the two supported generation types (KVM/Gen3 and XEN/Gen2), adding precision about what the tool does.

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 explicitly states which parameter combinations to use for KVM vs XEN (serverImageNo+serverSpecCode for KVM; serverImageProductCode+serverProductCode or serverImageNo+serverSpecCode for XEN). It also mentions dryRun=true for previewing without creating. It does not explicitly exclude alternative tools, but the guidance is strong for correct invocation.

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