k8s_scale_statefulset

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

With no annotations, the description carries full burden but only states the scaling action without behavioral details. It doesn't disclose that this is a destructive/mutative operation, potential impacts on pods, required permissions, or rate limits, leaving critical behavioral traits unspecified.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 mutative tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral effects (e.g., pod creation/deletion), error conditions, or return values, leaving significant gaps for safe and effective use by an AI agent.

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 schema already documents all parameters (name, namespace, replicas). The description adds no additional meaning beyond implying 'replicas' is the target count, matching the baseline score for high schema coverage.

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 target resource ('a StatefulSet'), specifying the operation to change the number of replicas. It distinguishes from siblings like 'k8s_scale_deployment' by targeting StatefulSets, but doesn't explicitly differentiate beyond the resource type.

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 is provided. It doesn't mention prerequisites like cluster access, compare to 'k8s_scale_deployment' for different resource types, or indicate scenarios like scaling for load changes versus using other tools for updates.

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