scale_deployment

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

Discloses that it modifies cluster state (destructive action) and provides safety mechanisms (confirmation, dry run). With no annotations, this achieves decent transparency, though it doesn't describe immediate consequences like rollout initiation.

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?

Two concise sentences, no wasted words. The 'WRITE ACTION' label at the start provides immediate understanding. Every sentence contributes essential guidance.

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 simple scaling tool with good parameter descriptions and usage hints, the description is mostly complete. Missing only potential return value details, but no output schema exists to necessitate that.

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 is 100%, but the description adds value by stating the dryRun default and its preview purpose. This goes beyond the schema to aid agent understanding.

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 verb ('Scales') and resource ('a Deployment'), distinguishing it from sibling tools (which are read-only or other operations). The upfront 'WRITE ACTION' label reinforces its purpose.

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?

Explicitly instructs to confirm with the user before calling and to use dryRun=true to preview. While it doesn't list specific alternatives, the context with sibling tools and the dry run guidance adequately guides usage.

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