k8s_get_kubernetes_cluster

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

With no annotations, the description must carry behavioral disclosure. It adds useful traits: 'Smart identifier resolution' and that the return includes configuration and status. However, it does not explicitly state that the operation is read-only, nor does it cover error behavior, permissions, or what happens if the identifier is not found.

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 compact, front-loads the core purpose, and uses a clean Args/Returns structure. Every sentence adds value; there is no restatement of the tool name 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 one-parameter read operation with an output schema available, the description covers the essential purpose, identifier semantics, and a summary of return contents. It could be more complete by distinguishing itself from the near-sibling k8s getter tools, but the core invocation needs are met.

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?

Schema coverage is 0%, so the description fully compensates by explaining the parameter's meaning, accepted forms (label or UUID), and giving concrete examples. For a single-parameter tool, this is complete and actionable.

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 states a specific verb and resource ('Get detailed information about a specific Kubernetes cluster') and adds scope with 'specific' vs. list tools. The return note 'including configuration and status' hints at breadth but does not explicitly differentiate from siblings like k8s_get_kubernetes_cluster_config or k8s_get_kubernetes_cluster_status.

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 context of when to use the tool is implied by the standard getter pattern, and the parameter guidance clarifies how to identify the cluster. However, there is no explicit statement about when not to use this tool or which alternative to prefer for only config, status, or resources, especially given the large k8s sibling group.

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