get_tkc_available_versions

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by detailing the return format (newest first), that it returns an empty list with error/hint if API unavailable, and the parameter roles. No contradiction with 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 very concise: two paragraphs plus parameter docs, no fluff. It front-loads the purpose with [READ] and a clear sentence, then provides essential details in a structured manner.

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?

With no output schema, the description adequately explains the return format ({versions: [...]}) and edge case (empty list with error). It covers the key behavioral aspects (ordering, error handling) and provides sufficient context for an agent to use the tool effectively.

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 bears full responsibility for explaining parameters. It describes 'namespace' as the vSphere Namespace for the Supervisor K8s API and 'target' as the vCenter (omit for default), adding meaningful context beyond the raw 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 it lists Kubernetes versions (TanzuKubernetesReleases) available on the Supervisor, using the verb 'list' and resource. It distinguishes itself from sibling tools like create_tkc_cluster and upgrade_tkc_cluster by explicitly noting it should be called before them to pick a valid 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?

The description explicitly says 'Call this before create_tkc_cluster or upgrade_tkc_cluster to pick a valid k8s_version,' providing clear guidance on when to use it. It also describes behavior when the API is unavailable, but does not explicitly state when not to use it or mention alternatives.

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