kubectl_scale

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

Annotations indicate destructiveHint=true, implying the tool can cause destructive changes. The description adds no further behavioral context, such as how scaling affects pods or whether it triggers rollout. Since annotations already cover the safety profile, the description marginally meets the bar.

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 short sentence, which is concise but under-specified. It is front-loaded but lacks important details, making it less effective than a more complete but still brief description.

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 omits return values, error conditions, or side effects. The focus on 'deployment' is misleading and incomplete, failing to cover the full scope of the tool.

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 100%, so the input schema documents all parameters. The tool description does not add any additional meaning beyond what is already in the schema, meeting the baseline but not compensating for any gaps.

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 states the verb 'Scale' and resource 'Kubernetes deployment', but it is inaccurate because the input schema allows scaling other resource types like replicaset and statefulset. This reduces clarity and differentiates it poorly from siblings like kubectl_patch or kubectl_rollout.

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 (e.g., kubectl_rollout for rolling updates). It lacks context about prerequisites, typical use cases, or exclusion criteria, leaving the agent without direction.

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