create_tkc_cluster

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

The description reveals the key behavioral trait of a dry-run mode that returns a YAML plan without applying, and that setting dry_run=False performs the actual creation. This adds significant value beyond annotations, which only indicate non-readOnly and non-destructive status. It does not contradict 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 well-structured with clear sections: a [WRITE] tag, purpose, important note, workflow, and args list. Every sentence is necessary and serves a purpose, making it concise yet informative.

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 tool's complexity (9 parameters, no output schema), the description covers the essential aspects: purpose, safety mechanism (dry_run), prerequisite workflow, and parameter details. It lacks information about return values on apply and error scenarios, but is otherwise complete for practical use.

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?

Although the schema properties have only titles, the description text provides per-parameter explanations with examples and constraints (e.g., control_plane_count '1 or 3', worker_count '>= 1'). This adds meaning beyond the schema, except for the 'target' parameter which is omitted from the description list.

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 starts with '[WRITE] Create a TanzuKubernetesCluster,' which clearly states the verb and resource. It distinguishes from sibling tools like scale_tkc_cluster and delete_tkc_cluster by focusing on creation, and the workflow references get_tkc_available_versions and list_vm_classes, which are distinct prerequisite 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?

The description provides explicit usage guidance by highlighting the dry_run default behavior and the recommended workflow of calling get_tkc_available_versions and list_vm_classes first. However, it does not explicitly state when not to use this tool or mention alternatives like scale or upgrade.

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