reboot_server

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

No annotations provided, so description carries full burden. It discloses the critical, destructive nature with a warning emoji, states that all services and the panel go down until boot completes, and requires a confirmation string. This is excellent transparency for a high-impact 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?

Two sentences with a leading warning emoji. Every word serves a purpose: what it does, impact, when to use, and required confirmation. No fluff. Front-loaded with critical information.

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 tool with one parameter, the description covers all necessary aspects: purpose, impact, usage context, and parameter requirement. No output schema needed; the outcome is implicit. Complete for safe decision-making.

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 coverage is 100% as the confirm parameter has a description in the schema. The description reinforces that the parameter must be exactly 'CONFIRMO' and implies it is mandatory despite the schema's required array being empty. This adds critical context about enforcement.

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 entire host machine, distinguishing it from sibling tools like restart_panel and restart_service. The wording 'Reinicia o SERVIDOR inteiro' and the warning about all services going down make the purpose explicit.

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?

Provides explicit guidance: 'Use apenas em manutenção planejada' (only for planned maintenance). It implies when not to use by highlighting the drastic impact. Could be improved by explicitly naming alternative tools for less severe restarts, but the context makes the guidance clear.

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