milehost_restart_server

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

No annotations are provided, so the description carries the full transparency burden. It only restates the core action and does not disclose effects like dropped connections, disrupted sessions, whether a restart is destructive, or whether an API key is genuinely required. For a disruptive operation, this is a notable gap.

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 first sentence is tight and front-loaded. The second sentence, 'AI AGENT MANDATE: Use this tool to restart the remote container,' repeats the same action and adds no new information, so not every sentence 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?

The tool has no annotations and no output schema, and it sits among many siblings with related functionality. The description does not clarify when this tool should be preferred over reboot alternatives, what happens after a restart, or how optional fields like folder_id should be resolved. This leaves the agent with incomplete context for confident invocation.

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 all three parameters already have documented meaning. The description adds no parameter-level detail, but the schema already handles parameter semantics adequately, keeping this at the baseline score.

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 clear verb and resource: 'Restarts the user server container on MileHost.' It is easy to tell what action the tool performs. However, it does not differentiate itself from similarly named siblings like milehost_reboot and milehost-reboot, so it lacks sibling differentiation.

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?

'AI AGENT MANDATE: Use this tool to restart the remote container' is an explicit instruction to use this tool for restarts, so the basic usage context is present. However, there is no guidance about when not to use it or which alternative should be chosen, especially given overlapping sibling tools such as milehost_reboot and milehost_run_command.

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