reboot_device

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It lists the reboot modes but does not warn that the operation will disconnect the device, may interrupt ongoing operations, or requires the device to be in a stable state. This is a significant gap for a state-changing action.

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 a single, clear sentence that leads with the action and resource, then lists the valid modes. No irrelevant information is included, and the structure is easy to scan.

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 tool's relative simplicity and 100% schema coverage, the description is adequate for a basic understanding. However, it lacks usage guidance, side-effect warnings, and prerequisite context (e.g., needing a connected device with proper authorization), which are not compensated by annotations.

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% for both parameters, and the description adds no additional meaning beyond what the schema already provides. The mode list is duplicated in the description and enum, so the baseline score of 3 applies.

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 function with a specific verb ('Reboot') and resource ('connected device'), and it enumerates the supported modes (system, bootloader, recovery, sideload), making it distinct from all sibling tools. No ambiguity exists.

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 implies the tool should be used when a device reboot is needed, but it does not explicitly contrast with alternative approaches (e.g., using execute_shell_command or other device-control tools). No prerequisites or exclusions are mentioned.

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