Restart a Kubernetes Deployment by updating its restartedAt annotation to trigger a rolling pod restart.
Roll a Deployment by setting restartedAt.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| namespace | No | ||
| session_name | No | default |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It discloses that it modifies a Deployment via restartedAt, but does not mention side effects, safety, permissions, or whether it triggers a rolling update. For a mutation operation, this is a significant gap.
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 with no fluff. It is appropriately front-loaded with the action. However, it is too terse, but that is a completeness issue, not conciseness. The structure is efficient.
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 lack of annotations and parameter descriptions, and an output schema that is not described, the description is insufficient. An agent cannot tell if it needs a connection, what happens on failure, or what the output means. It is not complete enough for safe 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 must explain parameters. It only refers to 'Deployment' but does not explain the 'name' parameter (presumably deployment name), 'namespace', or 'session_name'. The cryptic 'session_name' is unexplained.
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 'Roll' and resource 'Deployment', and the mechanism 'setting restartedAt'. This clearly distinguishes from siblings like k8s_scale or k8s_delete_pod.
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?
No guidance on when to use this tool versus alternatives. It does not mention scenarios, exclusions, or alternatives like scaling or pod deletion. An agent cannot infer when a rolling restart is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.