Reboot Server

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's mention of 'soft reboot' adds mild context about the nature of the reboot. However, it does not disclose side effects like connection loss or that the server must be powered on.

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 (11 words) that is front-loaded with the action. No redundant information; every word serves a purpose.

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 and no output schema, the description is nearly complete. It covers the action and method. Minor gap: no mention of required server state (e.g., must be running), but the sibling tools list provides context for alternatives.

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 input schema has 100% description coverage with 'Server ID' for the single parameter. The description only reinforces that the param identifies the server, adding no new semantic meaning beyond the schema.

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 uses specific verb 'send' and resource 'server' with explicit method 'ACPI reboot signal for a soft reboot'. This clearly states the action and distinguishes it from hard reset (hetzner_reset) and power operations (hetzner_power_off, hetzner_power_on).

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 implies usage for soft rebooting a server but does not explicitly state when to use this tool versus alternatives like hetzner_reset (hard reset) or hetzner_shutdown (graceful shutdown). No guidance on prerequisites or context is provided.

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