create_tkc_cluster

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

Annotations indicate a write operation (readOnlyHint=false), and the description adds behavioral context: dry-run mode, background provisioning, and return values. It complements annotations without contradiction.

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 well-structured with a clear header and bullet-like argument list. It is front-loaded with purpose. While slightly verbose, each sentence adds value.

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?

Given the complexity (9 parameters, no output schema), the description covers the process, prerequisites, and return behavior. It lacks output schema details and error handling, but is adequate for the context.

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 0%, but the description provides practical examples for each parameter (e.g., k8s_version: 'v1.28.4+vmware.1', vm_class: 'best-effort-large'). It explains dry_run and target, adding meaning beyond the bare 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 the verb 'Create' and the resource 'TanzuKubernetesCluster in a vSphere Namespace'. It distinguishes itself from sibling tools like scale_tkc_cluster and upgrade_tkc_cluster by specifying the creation action.

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 provides explicit when-to-use guidance: it explains the dry-run behavior, the need to poll get_tkc_cluster, and prerequisites such as calling get_tkc_available_versions and list_vm_classes first. It also notes that namespace must exist.

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