Retrieve detailed Kubernetes pod information, including status and containers, by specifying its name and namespace. Use it to inspect pod health and configuration for debugging.
Describe a Kubernetes pod (read details like status, containers, etc.)
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| namespace | Yes |
Changes observed during successful MCP inspections.
v0.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It signals a read-only operation via 'read details,' but says nothing about required permissions/RBAC, behavior when the pod or namespace does not exist, or the scope of the returned data — significant gaps for a tool with zero annotation coverage.
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 front-loaded sentence that states the action first and the payload second, with no wasted words. Its only shortcoming is that it is so terse it omits needed detail rather than adding any.
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 simple two-parameter read tool with no output schema, the description broadly conveys what comes back ('status, containers, etc.'), which is adequate. It is still incomplete because it neither explains parameter semantics nor error/edge-case behavior, and no annotations or output schema fill those 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% and there are two required parameters, so the description must compensate for the gap but does not. It never explains that 'name' identifies the pod and 'namespace' scopes it (or whether a default namespace applies), leaving the agent to infer both from the schema alone.
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 states a specific verb ('Describe') and resource ('Kubernetes pod'), with a parenthetical enumerating the details returned ('status, containers, etc.'). This clearly distinguishes it from siblings like list_pods and delete_pod, though it never names those alternatives explicitly.
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 phrase 'read details' implies this is the tool for inspecting a single pod, in contrast to list_pods for enumeration. However, there is no explicit when-to-use guidance, no prerequisites (e.g., pod must exist), and no named alternatives for the agent to choose between.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.