ncloud_nks_create_cluster

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

Annotations only state destructiveHint=false, so the description carries the burden of behavioral disclosure. It adds valuable details: missing required params cause 400 without details, G3/KVM requires specific hypervisorCode/softwareCode formats, and dryRun behavior. This is significant added context beyond annotations.

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 long, but the complex 16-parameter tool justifies the length. It is well-structured with headers and bullet points, front-loading the core purpose and dryRun tip. Every section adds necessary operational detail, though some redundancy exists with schema field descriptions.

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 description covers G2 vs G3 differences, required prerequisites, error behavior for missing params, and cross-references to other tools for values. It lacks explicit return value description (no output schema) and permission requirements, but for a create operation with a rich schema, it is remarkably complete.

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%, so baseline is 3. The description adds value by explaining G3 vs G2 parameter requirements (clusterType, k8sVersion, hypervisorCode, storageSize) and emphasizing the full softwareCode format. This goes beyond the schema's individual field descriptions.

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 NKS Kubernetes cluster' — a specific verb and resource that immediately distinguishes it from sibling tools like upgrade_cluster or delete_cluster. It also mentions dryRun for preview, adding further clarity.

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 clear context on when to use dryRun and explicitly references other tools (ncloud_nks_get_server_images, ncloud_nks_get_server_specs) for obtaining required values. It does not explicitly state alternatives/exclusions like 'use list_clusters to view existing clusters', but the usage context is strong.

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