scale_tkc_cluster

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

Adds detail beyond annotations: describes async nature, immediate return, polling recommendation, and that only workers are scaled. Confirms non-destructive intent but warns about draining nodes, aligning with destructiveHint=false.

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?

Well-structured with header, async note, and args list. Slightly verbose but each sentence contributes value. Could compress the args list into a table or shorter form, but remains clear and easy to parse.

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?

Complete for a 5-param tool with no output schema: describes return format, polling mechanism, and distinguishes from sibling tools. No gaps in explaining usage, behavior, or parameters.

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?

With 0% schema coverage, the description fully compensates by explaining each parameter's meaning, constraints (worker_count >= 1), and usage tips (omit pool_name for first, target for default). This is essential for correct invocation.

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 tool scales the worker node count of an existing TKC. It distinguishes from upgrade_tkc_cluster by specifying that upgrades are for K8s versions, and from create_tkc_cluster by targeting existing clusters.

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?

Explicitly tells when to use this tool (scale workers) and when to use upgrade_tkc_cluster instead (change K8s version). Also explains async behavior and that lowering worker_count drains nodes, setting clear expectations.

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