scale_deployment

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

No annotations provided, so description carries full burden. Discloses risk=medium, return of previous_replicas for undo, dry_run behavior, and that preview records no undo. Could mention pod termination side effects but adequate for a scaling tool.

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?

Highly concise and well-structured: risk tag, main action, returns, then Args in a clear list. No redundant sentences; every line adds value.

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 return value and dry_run behavior, essential for a scaling tool. Could mention error scenarios or that scaling affects deployment spec, but sufficient given no output schema and sibling context.

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 has 0% description coverage, but the Args section in the description briefly explains all 5 parameters (name, replicas, namespace, dry_run, target). Adds meaning beyond schema titles, though descriptions are minimal.

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?

Describes scaling a deployment with specific verb 'Scale' and resource 'deployment'. Distinguishes from sibling 'scale_statefulset' by naming the resource type directly. The inverse and undo features clarify uniqueness.

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?

Implies safe scaling via 'Returns previous_replicas so the change can be undone' and dry_run preview. However, lacks explicit guidance on when to use this vs other scaling tools like rollout_restart_deployment or set_deployment_image.

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