get_k8s_cluster

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

The description adds meaningful behavioral context beyond the readOnlyHint annotation by specifying exactly what information is returned and how it supports upgrade planning. Since there is no output schema, this detail is valuable and gives the agent a strong sense of the tool's behavior without contradicting annotations.

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 two sentences long and every clause earns its place: the first defines scope and output, the second provides actionable upgrade context. It is front-loaded and contains no 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?

Given the tool's moderate complexity, no output schema, and readOnly annotation, the description covers the main return values and a key use case (pre-upgrade checks). It could be slightly more complete by explicitly noting that this is for a single cluster and that list_k8s_clusters serves the multi-cluster case, but the core context is 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 input schema already has 100% description coverage for both parameters, so the description does not need to explain them. It adds no additional parameter-level semantics beyond reinforcing that k8s_cluster_id identifies a specific cluster, which is already implied by 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 clearly states the operation: 'Get details of a specific Kubernetes cluster' and enumerates the returned attributes (state, version, maintenance window, allow list, public/private). This distinguishes it from list_k8s_clusters and other get_* siblings by targeting a single cluster with a specific ID.

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 gives explicit guidance: 'Read this before an upgrade' and explains how the returned fields (availableUpgradeVersions, viableNodePoolVersions) relate to update_k8s_cluster. It lacks an explicit 'when not to use' or a direct comparison with list_k8s_clusters, but the intended context is clear.

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