flipper_reboot

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

Contradicts annotations: annotations state destructiveHint=false, but description implies DFU/UPDATE modes are destructive by requiring the destructive flag. This is a clear contradiction, reducing transparency.

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?

Two concise sentences with no wasted words. First sentence states purpose, second adds mode details. Well-structured.

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 purpose and mode behavior adequately for a simple tool with only two parameters. Could mention typical effects or post-reboot state, but not essential given the tool's simplicity.

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?

Adds meaning to the 'mode' parameter beyond the schema enum by explaining behavior and destructive requirement. The 'port' parameter is already described in the schema. Overall, compensates for schema coverage gap.

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?

Clearly states 'Reboot the device' and distinguishes between OS (normal) and DFU/UPDATE modes. This is specific and differentiates from sibling tools like flipper_disconnect.

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?

Explains that OS mode is a normal restart and DFU/UPDATE require a destructive flag, guiding mode selection. However, it does not explicitly state when to use this tool versus alternatives, though none are direct competitors.

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