Get Kubernetes cluster config

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

Beyond the annotations, the description discloses that the payload is a credential granting cluster access, that it should be treated as sensitive, and that a read-write API key is required. That auth-scope nuance is genuinely useful given readOnlyHint=true, and it does not contradict the annotation since the tool itself still performs a read. It does not mention expiry/rotation of the kubeconfig 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?

Two short sentences, zero filler, with the core action and return format front-loaded and the sensitivity/auth caveat following. Every sentence carries information an agent needs.

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 tool with full annotation coverage, the description covers what is returned, why it matters, and the credential scope required. The only remaining gap is lifecycle detail (whether the kubeconfig expires or must be rotated), which is minor but non-trivial for a credential-returning tool.

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 single parameter has full schema description coverage, including that the UUID comes from list_kubernetes_clusters, so the schema already carries the semantics. The description adds nothing about the id parameter, which is acceptable at 100% coverage but earns only the baseline.

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 names a specific verb and resource (get the kubeconfig for a cluster) and adds the return format (YAML) plus its practical purpose (connect kubectl and other Kubernetes tooling). It implicitly separates itself from get_kubernetes_cluster by emphasizing credentials rather than cluster metadata, but it never names that sibling explicitly.

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?

It gives clear usage context — you fetch this when you need to connect kubectl or other tooling — and states an auth prerequisite (a read-write API key). It stops short of explicit when-not guidance or naming alternatives such as list_kubernetes_clusters or get_kubernetes_cluster as the source of the id.

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