system_reboot

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

There are no annotations, so the description must disclose behavioral traits. It warns that the SSH session will be disconnected, which is a relevant side effect. However, it omits other significant effects such as termination of all processes, loss of unsaved changes, and downtime duration. This is insufficient for a destructive operation.

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 extremely concise, with two sentences that serve clear purposes: stating the action and issuing a warning. No wasted 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?

For a simple reboot command with one optional parameter and no output schema, the description is somewhat incomplete. It should mention the broader impact of the reboot (e.g., all connections dropped, service downtime) and perhaps note the delay parameter. The warning about SSH covers only one aspect of the operation.

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 already documents the delay parameter with a clear description (delay in seconds, default 0). The tool description adds no additional meaning, so it relies on the schema. Given the schema coverage is 100%, a baseline score of 3 is appropriate.

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 OpenWrt router,' using a specific verb and resource. It distinguishes from sibling tools like network_restart or service_action by indicating a full system reboot.

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 provides no guidance on when to use reboot versus alternatives like network_restart or service_action. It only states the action and a warning, leaving the agent to infer the appropriate usage.

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