hcloud_server_poweroff_action

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

The annotations already declare destructiveHint=true, but the description adds concrete behavioral context: it cuts power, gives the OS no time to gracefully stop, may cause data loss, and is equivalent to pulling the power cord. This is meaningful disclosure beyond the structured annotation, and it does not contradict the safety profile.

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 front-loaded with the action and then provides the critical risk context in a short sequence. Every sentence contributes to understanding the action's severity and appropriate use, with no irrelevant material.

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 destructive server action with complete parameter documentation, destructive annotations, and no output schema, the description covers purpose, risk, and alternative usage. It gives an agent enough to decide when to call it and what behavior to expect.

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 description coverage is 100%, and both the server id and wait parameters are documented directly in the schema. The description adds no parameter-specific meaning beyond the schema, so the 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 states a specific verb and resource: powering off a server. It immediately distinguishes this from a graceful shutdown by explaining that it cuts power and forcefully stops the server, so an agent can differentiate it from siblings like hcloud_server_shutdown_action.

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?

It explicitly says power off should only be used when shutdown does not work, which gives a clear when-to-use condition and names the preferred alternative. This is exactly the routing guidance an agent needs to avoid using the forceful action unnecessarily.

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