ncloud_nks_update_node_pool

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the agent knows it's safe and retriable. The description adds that it updates node count or autoscale, which is useful context, but does not disclose any additional behavioral traits (e.g., authorization needs, rate limits, side effects).

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 sentence with 10 words, front-loaded with the verb. No redundant information; every word 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?

The description is minimal for a mutation tool with 4 parameters (2 required) and no output schema. It does not mention required identifiers (clusterUuid, instanceNo), possible parameter combinations, or prerequisites. While annotations mitigate some risk, the description lacks sufficient context for correct invocation.

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 parameters are individually described. The description adds high-level purpose ('node count or autoscale') that ties the parameters together, clarifying the update intent. However, it does not explain mutual exclusivity or constraints beyond what the schema provides.

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 verb 'Update', the resource 'node pool settings', and the scope 'in an NKS cluster'. It specifies two specific update types (node count or autoscale), which differentiates it from sibling tools like update_node_pool_label or update_node_pool_taint.

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 for updating node count or autoscale but does not explicitly state when to use this tool versus alternatives (e.g., for labels use ncloud_nks_update_node_pool_label). No exclusion criteria or prerequisites are mentioned.

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