reboot

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

Disclosures that BLE link drops during restart and that DFU/UPDATE are real bootloader modes. Annotations already indicate destructiveHint=true, so the description adds value by specifying the impact on connectivity.

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 sentence with a warning, efficiently conveying purpose and critical usage notes. No unnecessary words.

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?

Covers the essential behavioral and parameter details. With an output schema present, absence of return value documentation is acceptable. Could mention error states or prerequisites, but overall sufficiently complete for a reboot tool.

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 schema only defines mode with a default but no description. The description fully explains each mode (OS, DFU, UPDATE) and their roles, compensating for 0% schema description coverage.

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 'Reboot the Flipper over BLE (system_reboot)' with specific modes. While it doesn't explicitly compare to siblings, the verb 'reboot' is unambiguous and distinguishes it from other app tools.

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?

Explicitly advises using OS mode as a recovery action when the device is wedged and warns against using DFU/UPDATE unless intended. Provides clear usage context.

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