Kubernetes MCP Server

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

No annotations are provided, so the description carries full burden. 'Perform a rolling restart' implies a mutation operation that will cause downtime/restart of pods, but it doesn't disclose critical behavioral traits: whether it requires specific permissions, what 'rolling' means (e.g., pod-by-pod replacement), potential side effects, or error conditions. For a mutation tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a tool with two simple parameters and front-loads the essential information. Every word earns its place.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what happens during a rolling restart, what the expected outcome is, potential risks, or error handling. Given the complexity of Kubernetes operations and the lack of structured safety information, this description leaves too many questions unanswered for safe agent usage.

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 100%, so the schema already documents both parameters (name and namespace) with basic descriptions. The description doesn't add any parameter-specific information beyond what's in the schema - it doesn't explain what 'rolling restart' means for these parameters or provide usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('perform a rolling restart') and the target resource ('deployment'), making the purpose immediately understandable. It distinguishes from siblings like k8s_describe_deployment or k8s_update_deployment_image by focusing specifically on restarting. However, it doesn't explicitly differentiate from k8s_rollout_undo which might also affect deployment state.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., deployment must exist), when to choose restart over other update methods, or what scenarios warrant a rolling restart versus other operations. With many sibling tools available, this lack of contextual guidance is a significant gap.

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