rollout_restart

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

The description discloses that the tool patches the pod template annotation to trigger a rolling restart, which implies a mutating operation. However, it does not explain side effects such as pod recreation, necessary permissions, or whether the operation is reversible. With no annotations provided, the description carries the full burden but only partially meets it.

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?

A single, concise sentence that communicates the core action and method without unnecessary words. It is front-loaded with the verb and resource.

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?

With no annotations, no output schema, and minimal parameter descriptions, the one-sentence description leaves significant gaps. It does not cover when to use the tool, what the parameters mean, what the user should expect after execution, or any safety considerations.

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?

The schema has zero description coverage, and the tool description does not explain the parameters ('name', 'namespace', 'cluster_alias'). The description only references the Deployment, leaving the parameter meanings to be inferred from their names, which may not be sufficient for an agent.

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 action ('Trigger a rolling restart') and the resource ('Deployment'), with the mechanism ('patching the pod template annotation'). This distinguishes it from sibling tools like scale_deployment or rollback_deployment by specifying the exact operation.

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 no guidance on when to use this tool versus alternatives such as scale_deployment or rollback_deployment. It only states what it does, leaving the agent to infer the appropriate context.

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