ncloud_nks_list_node_pools

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

readOnlyHint=true already declares this a safe read, so the bar is lower. The description adds only the cluster-scoping context, without disclosing return shape, pagination behavior, or empty-result handling.

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?

A single front-loaded sentence with zero filler; the scope qualifier follows the core action cleanly.

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 simple two-parameter read tool with annotations covering safety and no output schema, this is roughly adequate. Still, it omits any mention of the hypervisor filter's effect on results and gives no sense of what a returned node pool contains.

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 both parameters (clusterUuid and hypervisorCode) are fully documented in the schema. The description references the cluster scope but says nothing about the hypervisor filter or its XEN/KVM enum, so it adds little beyond the schema baseline.

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 clear verb (List) and resource (node pools) scoped to an NKS cluster, which lets an agent distinguish it from write siblings like ncloud_nks_create_node_pool or ncloud_nks_delete_node_pool. It does not, however, name any sibling explicitly or clarify the relationship to ncloud_nks_list_worker_nodes.

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?

Usage is only implied by the 'List' verb; there is no explicit when-to-use guidance, no note on prerequisites (e.g., a valid cluster UUID being required), and no routing to alternatives such as list_worker_nodes.

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