get_tkc_available_versions

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

The description adds behavioral context beyond annotations, such as the return format (sorted newest first), error handling (returns empty list with error and hint instead of raising), and explicitly states 'Read-only, no side effects'. Annotations already declare readOnlyHint and idempotentHint, but the description enriches this with specific details.

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 concise and well-structured. It starts with a clear purpose line, then details return format, error handling, usage guidance, and parameter descriptions in a logical order. Every sentence adds value without redundancy.

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 tool with 2 parameters, no output schema, and no nested objects, the description is complete. It covers return format, sorting, error handling, parameter semantics, and usage context. No essential information is missing.

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?

With 0% schema description coverage, the description fully explains both parameters: 'namespace' as the vSphere Namespace to reach the Supervisor K8s API, and 'target' as an optional vCenter entry in the config file. It clarifies default behavior for 'target', adding significant value beyond the 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 available on the Supervisor, using the verb 'list' and specific resource 'TanzuKubernetesReleases'. It distinguishes itself from sibling tools like 'create_tkc_cluster' and 'upgrade_tkc_cluster' by being a read-only listing operation and explicitly suggests calling it before those tools.

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 says 'Call this before create_tkc_cluster or upgrade_tkc_cluster to pick a valid k8s_version', providing clear when-to-use guidance. It also describes error behavior when the API is unavailable, which helps the agent decide when to use it.

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