docker_restart

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

The description explicitly states 'This changes server state,' which signals a side effect. However, with no annotations provided, it misses other behaviors like whether it requires root/sudo, possible downtime, or if it preserves container settings. The statement is helpful but incomplete.

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 short, containing only two sentences. The first sentence is action-oriented and front-loaded. It could be even more concise if the second sentence were omitted, but it adds value by signaling behavioral impact.

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 low schema coverage and no annotations, the description should provide more context about return values (especially since an output schema exists), error cases (e.g., container not running), and usage context. It is minimally acceptable for a simple restart operation but not comprehensive.

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?

The only parameter 'container' is minimally described in the schema (just a string), and the description adds no extra meaning. Since schema description coverage is 0%, the description does not compensate. Baseline is 3 due to low coverage and lack of additional info.

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 uses a specific verb and resource ('Restart a Docker container'), which clearly indicates the action. It is distinct from sibling tools like 'docker_stop' and 'docker_start', though it doesn't explicitly differentiate from 'docker_compose_restart', which is for Compose services.

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 like 'docker_stop' followed by 'docker_start', or the Compose variant. There is no mention of prerequisites, conditions for safe restart, or when to avoid using it.

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