ncloud_nks_list_clusters

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the 'current region' scoping constraint, but does not describe return format, pagination, or ordering. With annotations covering the safety profile, this is adequate but not rich in additional behavioral context.

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, front-loaded sentence with no filler or redundant information. It expands the NKS acronym, states the action (list), the resource (clusters), and the scope (current region), all in one concise line.

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 zero-parameter, read-only list operation with clear purpose and scope, the description is sufficient. It does not describe the response contents, but given the simple nature and absence of an output schema, this is acceptable. The description is not severely incomplete and supports correct tool selection.

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?

The input schema has zero parameters, so schema coverage is effectively 100%. The description adds contextual meaning by clarifying the 'current region' scope, which is not a parameter but a useful environmental constraint. Baseline for 0 params is 4, and the description does not contradict the schema.

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 uses a specific verb+resource structure: 'List all NKS (Ncloud Kubernetes Service) clusters' and adds 'in the current region' as scope. This clearly distinguishes it from sibling tools like ncloud_nks_get_cluster (single cluster) and ncloud_nks_list_node_pools (node pools).

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 when to use the tool: when you need to enumerate all NKS clusters in the current region. It provides clear context but does not explicitly mention when not to use it or point to alternatives such as ncloud_nks_get_cluster for detailed cluster info. This fits 'clear context, no exclusions'.

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