scale_tkc_cluster

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

The description adds the '[WRITE]' label, which aligns with annotations indicating a non-read operation, but provides no additional behavioral context such as potential downtime, permissions needed, or side effects. Annotations already convey the write nature, so the description's marginal value is low.

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 exceptionally concise: one line for purpose followed by a bullet-like parameter list. No redundant or irrelevant content.

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?

The description lacks crucial context for a mutation operation: no information on return value, operation asynchrony, error conditions, or prerequisites. Despite simplicity, the gaps are significant for an agent to invoke correctly.

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 covers three of four parameters with brief semantics, including a constraint for worker_count (>=1). However, it omits the optional 'target' parameter entirely. Given 0% schema coverage, the description partially compensates but is incomplete.

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 action ('Scale TKC cluster worker node count') and the specific resource, distinguishing it from sibling tools like create_tkc_cluster or upgrade_tkc_cluster. The verb-resource combination is precise and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., upgrade_tkc_cluster for version changes). The description only states what the tool does without context for appropriate usage scenarios or exclusions.

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