scale_statefulset

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

No annotations; description provides some behavioral context (write, risk, dry_run behavior) but misses side effects (pod termination, creation), prerequisites, error handling, and statefulness implications.

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?

Well-structured with header and Args; relatively concise. Minor extra info (inverse) but not harmful.

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?

Covers all parameters; lacks return value description and prerequisites. Given no output schema and 5 params, mild gaps in completeness.

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 coverage 0%, but Arg section explains all 5 parameters: name, replicas, namespace, dry_run, target. Clarifies default namespace and dry_run purpose.

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?

Verb "Scale" + resource "StatefulSet" clearly stated. Distinguishes from siblings like scale_deployment. Inverse operation mentioned adds clarity.

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?

Mentions dry_run for preview; no explicit when-to-use vs alternatives or exclusions. Name and resource type imply usage, but lacks explicit guidance.

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