gatekeeper_restart_container

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

Annotations already indicate the call is not read-only and is not marked destructive, and the description does not contradict that. But the description adds no behavioral context: no mention of container downtime, effect on running processes, requirement that the container exist, or what happens on failure.

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 short sentence with no filler, and the action is front-loaded. It is concise, though the brevity comes from under-specification rather than deliberate completeness.

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 one-parameter tool this is near-minimal, but it omits the operational context an agent needs: how the container is identified, prerequisite state, and how this relates to the many sibling start/stop/restart container tools. With no output schema, some effect or return information would meaningfully improve completeness.

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 schema has one required string parameter `name` with 0% description coverage. The description does not clarify whether `name` is a Docker container name, a container ID, or a Gatekeeper-managed container handle, and it gives no format or example.

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?

Uses an explicit verb + resource ('Restart a container'), so the core operation is clear. However, it does not distinguish this tool from sibling tools like restart_container, start_container, or gatekeeper_start_container; it mostly restates the tool name.

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 given about when to use restart versus start or stop, nor when to prefer this gatekeeper-specific variant over the generic restart_container sibling. The description leaves all selection logic to inference.

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