Restart a named Docker container on your homelab or a remote server. Quickly recover from crashes or apply new settings without manual commands.
Restart a Docker container by name
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Container name to restart | |
| server | No | Remote server name from config (optional, runs locally if omitted) |
Changes observed during successful MCP inspections.
v0.10.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are present, the description must compensate but fails to disclose any behavioral details beyond the action name. There is no mention of whether the operation is destructive, permissions required, asynchronous behavior, or return value, which are critical for agent decision-making.
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 concise sentence that efficiently conveys the core action. It is appropriately sized for a simple tool, though it could benefit from minor structural improvements.
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's simplicity, the description provides minimal but adequate information. However, the lack of annotations, output schema, and usage guidance leaves gaps in contextual completeness for an agent.
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 coverage is 100%, with both parameters well-described in the schema. The description adds no additional meaning beyond what the schema already provides, meeting the baseline but not exceeding it.
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?
Description clearly states the action (restart) and resource (Docker container by name), making the purpose unambiguous. It does not differentiate from sibling tools like docker_stop, but that is not necessary for minimal clarity.
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 is provided on when to use this tool versus alternatives (e.g., docker_stop followed by docker_start) or any prerequisites. The description lacks contextual usage information entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.