k8s_scale_deployment

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

Only warns '[DANGEROUS]' but does not describe behavioral traits beyond what the name implies. Missing details on destructive effects (pod termination, scaling behavior), required permissions, or side effects. Annotations are absent, so description carries full burden but falls short.

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?

Extremely concise but at the expense of essential information. The single sentence fails to cover parameter semantics, usage context, or results. For a 4-parameter tool with no schema descriptions, this is under-specified.

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 complexity of scaling a Kubernetes deployment (state change, potential disruption) and no output schema, the description lacks necessary context about outcomes, prerequisites, and safety. Incomplete for an AI agent to use 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?

Schema description coverage is 0% and the description only hints at the 'replicas' parameter ('specified number of replicas'). Does not explain 'name', 'namespace', or 'confirm' (safety flag), leaving 3 of 4 parameters undocumented.

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?

Clearly states the action (scale) and resource (Kubernetes deployment) with the specific outcome (to specified number of replicas). Distinguishes from sibling tools like k8s_deployment_list or k8s_pod_list.

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 on when to use this tool versus alternatives. Does not mention prerequisites, safety confirmations, or conditions that favor other sibling tools.

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