ncloud_nks_get_cluster

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

The readOnlyHint annotation already signals a safe read operation, and the description is consistent with that. However, the description adds no extra behavioral context such as what fields are returned, whether the response is paginated, or any caveats. It does not contradict the annotation but also provides minimal added value beyond it.

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, short sentence that directly states the tool's purpose without any redundant or irrelevant information. It is extremely concise and front-loaded, making it easy to parse quickly.

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 get-by-ID tool with one parameter and a readOnly annotation, the description is adequate but not rich. It does not specify what 'detailed information' includes (e.g., status, node pools, network config), which would be helpful since there is no output schema. Still, the tool's simplicity and annotations reduce the need for extensive elaboration.

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 schema has 100% description coverage for the single parameter clusterUuid, which is clearly documented as 'UUID of the cluster to query'. The tool description does not add any additional parameter meaning or usage nuance, so the schema carries the full burden.

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 the specific verb 'Get' and clearly identifies the resource as 'a specific NKS cluster', distinguishing it from list operations like ncloud_nks_list_clusters. The inclusion of 'specific' aligns with the required clusterUuid parameter, making the tool's purpose unambiguous.

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 this tool is used when a specific cluster UUID is already known, but it does not explicitly state when to use this over alternatives like list_clusters, nor does it mention any prerequisites or exclusions. Guidance is only implied by the wording and the required parameter.

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