create_tkc_cluster

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

The description discloses critical behavior beyond annotations: the dry-run default, the need to pass dry_run=False for actual provisioning, background execution, the returned shape, and the polling requirement. This is exactly the kind of behavioral context an agent needs to invoke the tool safely.

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 compact and front-loaded, with every sentence contributing: purpose, dry-run behavior, return shape, background provisioning, polling, and prerequisites. There is no filler or 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 9-parameter creation tool with no output schema, the description covers the essential workflow: what happens by default, how to cause real creation, what to expect in the response, how to verify completion, and which prerequisite tools to call first. This is sufficient for correct selection and invocation.

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%, so the schema already documents every parameter's meaning, type, and default. The description adds workflow hints for k8s_version and vm_class, but it does not substantially improve on the schema's parameter documentation.

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 the exact action, 'Create a TanzuKubernetesCluster in a vSphere Namespace,' with a specific verb and resource. The [WRITE] marker and clear resource name distinguish it from sibling operations like get_tkc_cluster, scale_tkc_cluster, and delete_tkc_cluster.

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 clear operational guidance: it defaults to a dry run unless dry_run=False, requires calling get_tkc_available_versions and list_vm_classes first, and instructs polling get_tkc_cluster until the phase is running. It does not explicitly state when not to use it versus alternatives, but the create/read/update/delete sibling structure makes the intended use obvious.

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