hcloud_server_disable_backup_action

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

Annotations already flag destructiveHint=true, and the description adds crucial specifics beyond them: that existing backups are permanently deleted, that this is immediate, and that this ends backup charges. That goes well past what the structured hints convey.

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 destructive warning is front-loaded and prominent, and each sentence carries useful information. There is minor redundancy between the opening line and the title-like phrase, but it is efficient overall.

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 two-parameter destructive action with full schema coverage and annotations, the description supplies everything an agent needs: scope, irreversible consequence, and cost implication. Nothing material is missing.

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. The description adds no parameter-level detail, so the baseline 3 applies.

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 ('Disable') plus resource ('Backups for a Server') and immediately clarifies the secondary effect: existing backups are deleted. The purpose is unambiguous and clearly the inverse counterpart to hcloud_server_enable_backup_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?

The description gives a clear operational context and a prominent caution ('immediately removes all existing backups'), which implicitly guides when to invoke it carefully. It does not explicitly name the enable alternative or state preconditions, but the implied usage is strong.

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