hcloud_delete_volume

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

Annotations already declare destructiveHint=true, but the description adds valuable context beyond them: that all data is irreversibly destroyed and the two preconditions that cause failure. It does not describe error behavior when preconditions are unmet, but the added irreversibility and gating conditions are solid.

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 action and destructiveness. Minor redundancy between the title line 'Delete a Volume' and 'Deletes a volume', but the whole is short and every substantive sentence earns its place.

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 single-parameter destructive delete with full annotation coverage and no output schema, the description supplies everything needed to call it correctly: the id role is schema-documented, and the preconditions and irreversibility are spelled out.

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?

Only one parameter (id) with 100% schema description coverage, so the schema already documents it fully. The description adds no syntax or format detail, which is acceptable given high coverage – 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 and resource ('Delete a Volume') that unambiguously identifies the operation among the many hcloud siblings. An agent can immediately tell this is the volume-deletion tool.

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 states preconditions for use: the volume must not be attached to a Server and must not have delete protection enabled. It does not name alternative tools (e.g. hcloud_volume_detach_action or hcloud_volume_change_protection_action) that would unblock those conditions, so it stops short of full when/when-not routing.

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