ncloud_nks_create_node_pool

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

Beyond the sparse annotations (only destructiveHint=false), the description discloses preview behavior (dryRun) and a validation rule with an exact error code and effective date (400 on zone mismatch since 2026-09-17). This adds meaningful behavioral context about error conditions. No contradiction with 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?

Three focused sentences: purpose first, then preview tip, then key constraint. No filler or repetition beyond what's needed. Front-loaded with the core action.

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 the most critical non-obvious constraint (Regional cluster zone matching) and the preview workflow. The schema covers all 12 parameters, including nested objects. No output schema, but return values are typical for a create and less critical than the error condition disclosed. Could mention async behavior but not essential.

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 description coverage is 100%, so each parameter is already documented. The description only repeats zoneCode and dryRun behavior already present in the schema, adding no new parameter-level meaning. Baseline 3 is appropriate given the high schema coverage.

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?

States a specific verb ('Create'), resource ('node pool'), and context ('in an NKS cluster'). Clearly distinguishes from sibling node pool operations like list/update/delete by naming the create action. No ambiguity 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?

Gives clear contextual guidance for when the tool applies: preview via dryRun and the Regional-cluster zoneCode requirement. Does not name alternative tools (e.g., update/list), but the context is clear enough to guide invocation. Lacks explicit when-not-to-use/exclusion statements.

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