ncloud_nks_get_versions

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

The readOnlyHint annotation already signals this is a safe, read-only operation. The description adds context that it's for cluster creation, but no additional behavioral details (e.g., pagination, rate limits, or response structure) are disclosed. With annotations covering the safety profile, this is adequate but not exceptional.

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, 7-word sentence that is highly concise and directly states the tool's purpose. No extraneous information or filler.

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 no output schema, the description is largely complete—it tells what the tool does and implicitly what it returns (list of versions). However, specifying that it returns an array of version strings or objects would improve completeness. Still, it is functional.

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 100% description coverage for both parameters (hypervisorCode and isRegionalSupport), so the schema already provides meaning. The description does not add extra semantics beyond what the schema provides, hence a baseline score of 3 is appropriate.

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?

Description clearly states 'List available Kubernetes versions for NKS cluster creation', specifying a specific verb (list) and resource (Kubernetes versions for NKS cluster creation). It distinguishes itself from sibling tools like ncloud_nks_create_cluster or ncloud_nks_list_clusters by focusing on version listing.

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 when one needs to see available Kubernetes versions, but no explicit 'when not to use' or alternatives are provided. Given the sibling set includes many NKS tools, the purpose is clear enough to infer when to use this tool over others.

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