hcloud_server_reset_action

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds crucial context they cannot convey: loss of graceful shutdown and the risk of data loss, plus the power-cord analogy. It does not mention that the operation is asynchronous and returns an action object, which is a minor omission.

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?

Front-loaded with the outcome, then the warning, then the usage constraint. Slightly redundant in restating the force-stop consequence twice ('without time to gracefully stop' and 'pulling the power cord'), but every sentence still contributes risk or routing 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 no-output-schema, two-parameter mutation, the description covers the destructive nature, the data-loss risk, and the alternative. The only real omission is that the call is async and can be polled via the wait parameter, which the schema covers but the description does not connect.

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% with only two parameters, both fully described in the schema (id and wait/poll). The description adds nothing about either parameter, so it sits at the baseline where the schema carries the semantics.

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?

States a specific verb (reset) on a specific resource (Server) and immediately defines the semantics: cuts power and restarts without graceful OS shutdown. This clearly distinguishes it from the sibling reboot, poweroff, and poweron actions in the same family.

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?

Explicitly names the fallback condition: 'Reset should only be used when reboot does not work,' which routes the agent to hcloud_server_reboot_action first. That is a direct when-to-use/when-not-to-use rule with the alternative implied by name.

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