hcloud_server_disable_rescue_action

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

Goes well beyond the annotations by stating the setting change does not reboot the server and the agent must trigger that separately, plus the auto-expiry window and the effect on next boot. That is exactly the behavioral context an agent needs before calling a mutation with destructiveHint=true.

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 and short, with the reboot caveat placed last where it belongs. The heading and first sentence are near-duplicates ('Disable Rescue Mode for a Server' / 'Disables the Hetzner Rescue System for a Server'), so one sentence is wasted.

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?

Covers what the change does, when it happens, and the required follow-up reboot, which is complete for a no-output-schema flag toggle. It stops short of saying an action object is returned or how polling relates to the wait parameter, a minor gap given the rich schema.

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% and both parameters (id, wait) are documented in the schema, so the description need not repeat them. It adds no meaning beyond the schema, which is the baseline-3 case.

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?

Names a specific verb (disable) and resource (Hetzner Rescue System for a Server) and states the resulting state: the server boots from its disks. This is clearly distinct from siblings like hcloud_server_enable_rescue_action or hcloud_server_reboot_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?

Explains the operational context well, including that rescue mode auto-disables after first boot or 60 minutes of non-use, which tells an agent the call is often unnecessary. It does not explicitly name the counterpart tool (enable_rescue_action) or state exclusions, so it falls short of a full 5.

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