List Kubernetes versions

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the useful behavioral nuance that the result set shrinks to upgrade-compatible versions when current_version is supplied, but says nothing about ordering, catalog size, or whether the list reflects a live provider API.

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 sentences, zero filler, with the core purpose front-loaded and the filtering hint immediately after. Every sentence earns its place.

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?

This is a simple read-only catalog tool with full schema documentation and complete safety annotations, so little more is required. The only minor gap is that there is no output schema and the description does not characterize a version entry or the list's ordering.

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 description coverage is 100%, and all three parameters are documented in the schema, including the same 'valid upgrade targets' semantics for current_version. The description largely restates what the schema already says, so it stays at the baseline rather than adding meaning.

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 ('List the available Kubernetes versions'), which is clearly distinct from siblings such as list_kubernetes_clusters and list_kubernetes_packages. It does not explicitly state how it relates to those siblings, but the resource name alone removes ambiguity.

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 a concrete conditional: pass current_version when the goal is to find valid upgrade targets from a running cluster. That covers the main usage decision, though it offers no guidance on when to page through the full catalog versus filtering, and no stated prerequisites.

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