rollout_restart_deployment

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

No annotations are provided, so the description carries full burden. It indicates the operation is a write with medium risk and no clean undo, but does not detail side effects like pod replacement behavior, required permissions, or reversibility by other means.

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?

The description is concise: three sentences plus a bullet list, with the purpose and risk front-loaded. No unnecessary words; every sentence 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?

Given the tool's complexity (rolling restart) and lack of output schema, the description covers the core action and dry_run mode but omits details about the restart behavior, return values, and whether it causes downtime. Could be more complete for an agent.

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%, but the description meaningfully explains each parameter: name, namespace (with default behavior), dry_run (preview function), and target (config reference). This adds value beyond the schema's type/default information.

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 tool triggers a rolling restart of a deployment, distinguishing it from sibling tools like rollout_undo or rollout_status. The verb 'trigger' and resource 'rolling restart of a deployment' are specific.

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 mentions 'No clean undo' as a warning and suggests using dry_run preview, but does not compare to alternatives or provide explicit when-to-use or when-not-to-use guidance. It implies caution but lacks context relative to siblings.

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