scale_replicas_up

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

Includes [WRITE][risk=medium] tag, explains reversibility, dry_run preview behavior (reads current count and fails early if deployment doesn't exist). No annotations provided, so description carries full burden and does it well.

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-organized with a concise header, a bullet for dry_run behavior, and an Args list. A few extra words could be trimmed, but overall efficient and clear.

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, behavioral traits (reversible, dry_run, early failure), and usage context. With no output schema or annotations, this description fully enables correct agent invocation.

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 description's Args section adds full meaning for all five parameters, including that num_replicas must be higher, dry_run purpose, and target optional with default behavior.

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?

Clearly states the action ('raise a deployment's replica count') and the resource, and the reversibility note helps distinguish from sibling tools like scale_replicas_down and scale_to_zero.

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?

Provides explicit guidance on using dry_run=True for preview and explains the behavior. Implicitly differentiates from siblings by focusing on scaling up, but does not explicitly mention alternatives.

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