scale_statefulset

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

The description offers minimal behavioral detail. It does not explain whether scaling is synchronous, if it waits for rollout, permissions required, or behavior on non-existent StatefulSets. Since no annotations exist, the description carries the full burden but lacks depth.

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?

One-sentence description, front-loaded, with no extraneous content. It is as concise as possible while conveying the core action.

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?

For a mutating operation with no annotations and no output schema, the description is too terse. It fails to mention return behavior, error handling, or operational constraints that would help an agent invoke it safely.

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 only implies the 'replicas' parameter via 'specified number of replicas' but does not explain the 'name', 'namespace', or 'cluster_alias' parameters, leaving all but the most obvious semantics uncovered. With 0% schema coverage, the description should compensate but does not.

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 tool scales a StatefulSet to a specified replica count, using a specific verb and resource. It implicitly distinguishes from sibling tools targeting Deployments (scale_deployment) and DeploymentConfigs (scale_deploymentconfig).

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, preconditions, or alternatives. It simply states the action without any context about when to prefer it over other scaling tools.

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