ncloud_sourcedeploy_get_k8s_clusters

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

The readOnlyHint annotation already indicates the safe read-only nature. The description adds the scoping detail that results are limited to clusters available for SourceDeploy stage configuration, which is useful, but it does not describe return format, pagination, or error behavior.

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. It earns a perfect score for conciseness.

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?

Given the tool has no parameters and no output schema, the description provides the essential information: it returns a list of Kubernetes clusters available for SourceDeploy stage configuration. It's sufficient for a simple read-only list operation, though it could mention response fields if present.

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 tool has zero parameters, and the schema is trivially 100% covered. Per the baseline for no parameters, the description doesn't need to add parameter semantics; it simply describes the output.

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 ('Get the list') and the specific resource ('available Kubernetes Service clusters for SourceDeploy stage configuration'). This distinguishes it from sibling tools like ncloud_nks_list_clusters by scoping to SourceDeploy use.

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 phrase 'for SourceDeploy stage configuration' provides clear context on when this tool is relevant. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of the full 5.

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