rollout_restart_deployment

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

Annotations already declare destructiveHint=true and non-idempotent, so safety is partly covered. The description adds meaningful context beyond them: 'No clean undo' and the dry_run preview path, which is exactly the kind of operational guidance an agent needs before a mutating call.

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?

Front-loaded with the action and risk tag, followed by the dry_run preview note and a compact args list. Every line is useful, though the Args block is a slightly mechanical enumeration.

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 mutation tool with annotations covering the safety profile and no output schema, the description supplies the remaining essentials: operation class, irreversibility, and a safe preview mechanism. Nothing critical is missing for correct 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 description coverage is 0%, so the description carries the full burden and does list all four parameters. It adds real meaning for namespace ('omit for the target's default namespace') and target ('k8s target name from config'), but name and dry_run are essentially restatements of the parameter names, so it only partially compensates for the coverage gap.

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?

States a specific verb and resource ('Trigger a rolling restart of a deployment'), which cleanly separates it from siblings like rollout_undo_deployment, rollout_pause, and scale_deployment. The [WRITE] tag signals the operation class immediately.

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?

The description tells the agent how to preview safely (dry_run=True) and warns there is no clean undo, which implies caution. However, it never says when to choose this over adjacent tools such as rollout_undo_deployment or set_deployment_image, leaving the selection logic to inference.

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