milehost_reboot

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does state that the action restarts the container and all running processes, implying disruption of active work. It does not mention side effects such as lost sessions, permission requirements, or failure behavior, so transparency is partial.

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 compact and informative. The second sentence, the 'AI AGENT MANDATE' instruction, largely repeats the same idea and adds little informational value, though the overall description remains short.

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 reboot tool with all-optional parameters, the core behavior is adequately conveyed. However, the absence of an output schema, lack of description around return values or disruption, and ambiguity against restart/reboot siblings leave some gaps for an agent deciding whether and how to invoke it.

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 input schema already describes all three parameters with 100% coverage, so the baseline is 3. The description adds no additional parameter meaning, but the schema sufficiently documents the optional api_key, api_url, and folder_id.

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 clearly states the verb ('reboots') and the resource ('user server container and all running processes'), so the core operation is unambiguous. It is not explicitly differentiated from similarly named siblings like milehost_restart_server or milehost-reboot, which slightly lowers the score.

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 'AI AGENT MANDATE' sentence explicitly identifies the intended use case: perform a full clean reboot of the remote container. However, it does not explain when to choose this tool over milehost_restart_server, milehost-reboot, or milehost_run_command, nor does it state any exclusions or conditions.

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