get_tkc_available_versions

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds meaningful behavioral context: it returns results newest first, and it degrades gracefully with an empty versions list plus error/hint when the API is unavailable rather than raising. This goes beyond what the annotations convey.

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?

Three terse, purposeful sentences: the READ action, the return shape and ordering, and the error behavior plus usage guidance. Every sentence contributes value and the most important information is front-loaded.

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?

Even with no output schema, the description supplies the return shape, example version format, ordering, error behavior, and the exact workflow context. An agent has enough information to call this tool correctly and interpret the result.

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 100% and both parameters (target, namespace) already have descriptions in the schema. The tool description does not add deeper parameter semantics, but a baseline of 3 is appropriate since the schema carries the parameter documentation 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 states a specific verb ('List') and resource ('Kubernetes versions / TanzuKubernetesReleases available on the Supervisor'). It clearly differentiates this read-only query from the cluster lifecycle siblings (create_tkc_cluster, upgrade_tkc_cluster) by framing it as a prerequisite for choosing a valid k8s_version.

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 explicitly advises calling this before create_tkc_cluster or upgrade_tkc_cluster to pick a valid k8s_version, giving clear contextual placement. It does not explicitly list when not to use it or compare against sibling query tools, but the intended usage is unmistakable.

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