restart_deployment

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

No annotations are provided, so the description must disclose behavioral traits. It states the operation causes a restart but doesn't explain side effects (e.g., pod recreation, potential downtime) or whether it is destructive. The allowlist mention hints at restrictions but lacks detail.

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 very concise at one sentence (10 words). It is front-loaded with the action and resource. However, it could benefit from a structure that lists parameters or constraints more clearly.

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 has 2 required parameters, an output schema exists, and no annotations, the description is insufficient. It lacks details on return values, side effects, and prerequisites. The allowlist mention adds some context but overall leaves many gaps.

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%, yet the description adds no information about the two parameters (namespace and name). The agent must infer their roles from the tool name alone. The description should at least indicate that these identify the deployment to restart.

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 it performs a 'Rollout-restart' on a deployment, which is a specific verb-resource combination. It distinguishes from sibling tools like scale_deployment and delete_pod. However, it does not elaborate on what a rollout-restart entails, which might leave ambiguity.

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 a constraint (subject to allowlist) but provides no guidance on when to use this tool versus alternatives like scale_deployment. No explicit context for when a restart is appropriate or not.

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