ncloud_nks_list_node_pools

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

The description is consistent with the readOnlyHint annotation, confirming it's a read operation. However, it adds little beyond that: no mention of pagination, response format, or any side effects. The annotation already covers the safety profile, so the description provides minimal extra value.

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, concise sentence of 9 words that conveys the essential information without any unnecessary words or repetition. Efficient and well-structured.

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 list operation with one parameter and no output schema, the description is minimally adequate. It lacks details about what data is returned (e.g., node pool names, sizes, states) and whether results are paginated. The absence of an output schema places a higher burden on the description, which it does not fully meet.

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% with a clear description for clusterUuid. The description reinforces that this is the cluster identifier. However, it does not add any additional context (e.g., how to obtain the UUID, constraints on the value). Baseline 3 is appropriate given 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?

The description clearly states the action (list) and the resource (node pools in an NKS cluster). It unambiguously identifies the tool's function and distinguishes it from sibling tools like create/update/delete node pool.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., ncloud_nks_list_worker_nodes) or any prerequisites. The description simply states what it does, leaving the agent to infer usage context from the schema and tool name.

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