reboot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that bootloader/recovery modes are risky, may require physical buttons or flashing to return to normal use, and prompt for stronger confirmation. This goes beyond basic schema info and genuinely informs the agent of consequences.

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, front-loaded with the action, and every sentence adds meaningful information. The risk warning is placed after the core definition and is not redundant with the schema.

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 reboot tool with two parameters, the description handles the main 'mode' parameter thoroughly and output schema exists to cover return values. However, the complete absence of any explanation of the 'serial' parameter leaves a gap for an agent trying to target a specific device.

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 has 0% coverage, so the description is the only source of parameter meaning. It explains the 'mode' values and their risk implications well, but it says nothing about the 'serial' parameter, leaving its purpose and usage undocumented.

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 action ('device restart') and enumerates the supported modes, so an agent knows this is the reboot tool. It does not explicitly differentiate from siblings, but no other sibling performs a device reboot, so the lack of differentiation is not a practical problem.

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 description gives concrete usage context by explaining the three modes and explicitly warns that bootloader/recovery modes are higher risk and require stronger confirmation. It does not mention exclusions or alternative tools, but none are obviously relevant for a reboot operation.

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