kubectl_scale

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

Annotations already provide 'destructiveHint: true', indicating mutation. The description adds no further behavioral context, such as that scaling down may delete pods. Since the annotation carries the burden, a score of 3 is appropriate—it does not contradict but adds little beyond what annotations already convey.

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 a single concise sentence with no wasted words. It is front-loaded and to the point, which is ideal for quick comprehension.

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 has 5 parameters and no output schema, the description is overly brief. It does not explain the ability to scale different resource types, the effect of the 'replicas' parameter, or the optional context/namespace. The description should provide more context to be complete for effective use.

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?

All five parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description does not add any additional meaning or context for the parameters beyond the 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 the action 'scale' and the resource 'a Kubernetes deployment', providing a clear verb-resource pair. However, it is slightly narrow as the tool also supports scaling other resource types like replicasets and statefulsets as indicated by the 'resourceType' parameter, which is not mentioned in the description.

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 provides no guidance on when to use this tool versus alternatives like 'kubectl_patch' or 'kubectl_apply' for scaling. There is no mention of prerequisites, context, or exclusions, making it difficult for the agent to choose correctly among sibling tools.

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