reboot_device

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

The description discloses that active sessions and captures will be interruptedcompress and that the operation can be disabled via ALLOW_POWER_CONTROL=false. Since no annotations are provided, the description carries the full burden, and it reasonably addresses the most important behavioral impacts of a reboot.

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 three short sentences, with the primary action and immediate consequences stated upfrontлекс, followed by a critical configuration caveat. Every sentence adds meaningful information without excess.

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 zero-parameter input and simple action, the description covers the essential behavioral context, but could mention whether the reboot is graceful or forcedlint. The output schema exists, so return values are not the main gap.

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?

There are no parameters to document, and the schema is empty. The description properly conveys the tool's command, so the agent does not need parameter explanations. A baseline of 4 for zero-parameter tools is appropriate here.

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 action ('Reboot the WLAN Pi immediately') with a specific verb and resource, making it easy to distinguish from sibling tools like shutdown_device and restart_service. The immediacy is communicated, and the tool's destructive nature is implied effectively.

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?

While the description does not explicitly name alternatives, it implies use when an immediate reboot is required and warns that active sessions and captures will be interrupted. It also mentions the ALLOW_POWER_CONTROL=false config as a precondition/disable mechanism, which is useful context for deciding whether this tool will work.

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