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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds no behavioral context beyond them: it does not say what happens on success, whether scaling to 0 takes the workload down, or whether permissions are required. For a mutation tool, that is a meaningful gap.

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?

A single efficient sentence with the verb and target front-loaded and no filler. It is arguably too terse given the mutation involved, but there is no wasted text.

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 parameter surface is fully documented and there is no output schema to explain, so the essentials are present. However, for a non-idempotent mutation the description omits outcome and side-effect information an agent would want before calling it.

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 namespace, deployment_name, replicas, cluster_id and dry_run are all documented in the schema itself. The description contributes nothing extra (no format hints or cross-parameter relationships), so the baseline 3 applies.

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?

States a specific verb ('scale') and resource ('deployment') and names the unit of change (replicas). It does not distinguish itself from nearby siblings like scale_statefulset or restart_deployment, so it falls short of a 5.

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?

There is no when-to-use guidance, no prerequisites (does the deployment need to exist, does it need a running cluster), and no mention of the alternative scale_statefulset for StatefulSets. The agent has to infer usage entirely.

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