upgrade_tkc_cluster

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds [WRITE] but does not elaborate on potential impacts like downtime or prerequisites. Minimal additional context beyond 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?

Two short paragraphs, front-loaded with purpose. Every sentence adds value. No wasted words.

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?

Missing explanation of the optional 'target' parameter and no description of return value or output. For a mutation with no output schema, more details on expected result would improve completeness.

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?

The description explains three required parameters (name, namespace, k8s_version) and suggests using get_tkc_available_versions for k8s_version. The optional 'target' parameter is not described, but schema coverage is 0%, so description compensates well for most.

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 upgrades a TKC cluster to a new K8s version. The verb 'upgrade' and resource 'TKC cluster' are specific, and it distinguishes from sibling tools like create, delete, scale.

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 advises using get_tkc_available_versions to list available versions, guiding correct usage. It also includes a [WRITE] tag indicating mutation. While it doesn't explicitly list when not to use, the advice is clear enough.

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