vyos_reboot

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

The description warns that the reboot is immediate and will interrupt all active sessions and traffic, which is critical behavioral information. With no annotations, this warning provides adequate transparency about the destructive nature, though it does not discuss return behavior or confirmation requirements.

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--two sentences plus a warning--with no unnecessary words. Every part earns its place, and the warning is properly emphasized.

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?

While the description covers the action and key warning, it lacks information about what the tool returns (e.g., success message, status code) and whether it blocks until reboot completes. Given no output schema, this is a gap.

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?

There are zero parameters, so the description does not need to add parameter meaning. Per guidelines, baseline is 4. The description does not introduce confusion.

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 it reboots the VyOS router, using a specific verb and resource. However, it does not differentiate from the sibling tool vyos_poweroff, which might perform a similar action but potentially with different semantics.

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?

No guidance is provided on when to use this tool vs. alternatives like vyos_poweroff or vyos_reset. There is no context about prerequisites or situations where reboot is appropriate.

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