milehost-reboot

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

With no annotations, the description carries the burden of behavioral disclosure. It states that the tool restarts the container and all running processes and emphasizes a 'full clean reboot,' which conveys the core impact. However, it does not disclose downtime, session interruption, authentication requirements, or potential side effects.

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 short, but the second sentence is largely redundant with the first, restating that the tool performs a full reboot. It is not a concise, waste-free definition, though it remains readable and quick to parse.

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 description covers the core action but is incomplete for a tool with no output schema and no annotations. It does not describe return values, errors, whether confirmation is needed, or what happens if the API key or folder_id are absent.

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 optional parameters are already documented in the schema. The description adds no additional meaning about api_key, api_url, or folder_id beyond what is provided, meriting only 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 clearly states the tool's action: rebooting and restarting the user server container and all running processes on MileHost. It is more specific than a bare verb, but it does not differentiate itself from closely related siblings such as milehost_restart_server or milehost_reboot.

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 tells the agent to use this tool when a full clean reboot is needed. It provides clear activation context, though it does not mention exclusions, alternatives, or when the sibling restart tools should be preferred.

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