delete_tkc_cluster

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds behavioral details: the tool rejects deletion if workloads are running (unless force=True), dry_run defaults to True, and confirmed is required. This goes beyond annotations by explaining safety gates.

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, well-structured with a [WRITE] tag, safety note, and bullet points. Every sentence provides essential information 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?

Given the tool's destructive nature and the lack of output schema, the description adequately covers safety, defaults, and required parameters. It lacks details on return values or error messages, but the context is sufficiently complete for an agent to use safely.

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 description must explain parameters. It explains 5 of 6 parameters (name, namespace, confirmed, dry_run, force) with their roles and defaults. 'target' is listed but not described. Overall, it adds significant meaning beyond 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 'Delete a TKC cluster' with a [WRITE] tag, specifying the verb and resource. It distinguishes itself from siblings like create_tkc_cluster and upgrade_tkc_cluster by focusing on deletion.

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 explains when to use (to delete) and provides critical usage details: dry_run=True by default, need confirmed=True to proceed, and force option to skip workload checks. It does not explicitly contrast with siblings but gives clear conditions for safe use.

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