hcloud_server_backup

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

Annotations already declare this is a non-read-only, destructive, open-world mutation. The description's framing as a benign 'toggle' adds little beyond that and omits the operationally important facts: disabling backups destroys existing backup history and enabling incurs extra cost. It doesn't contradict the annotations, but it under-discloses the destructive side.

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 short sentences with no filler; the core action is front-loaded. It is arguably too terse for the gaps it leaves, but nothing in the text 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?

No output schema exists, so the description could carry more. For a destructive, billing-relevant server mutation it omits what happens to previously taken backups, whether the call is synchronous when `wait` is set, and what the response reports. Adequate but clearly incomplete for the risk profile.

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 only 33%: `enable` is documented in the schema, `id` is self-explanatory, but `wait` (default true) is undocumented in both places. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap.

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 and resource: toggling Hetzner-managed automatic backups on a server, and names the underlying enable_backup / disable_backup actions. It is clear what the tool does, though it doesn't tell the agent why this wrapper differs from the two action siblings it names.

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 mentions enable_backup / disable_backup actions but gives no condition for choosing this wrapper over hcloud_server_enable_backup_action or hcloud_server_disable_backup_action. There is no when-to-use, when-not-to-use, or prerequisite guidance.

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