hcloud_update_volume

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

The annotations already declare this is a destructive, non-read-only update, but the description adds no behavioral context. In particular, it does not mention that labels overwrite the existing label set, which is important for a destructive update.

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 two sentences are redundant: the first restates the tool name and the second paraphrases it without adding information. Brevity here reflects under-specification rather than efficient communication.

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?

This is a destructive mutation tool with no output schema and a nested request body, yet the description says nothing about what changes, what gets overwritten, or operational effects. Annotations and schema provide some safety context, but the description remains materially incomplete.

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 50%, and the description provides no parameter-level detail. The schema documents id, name, and labels reasonably well, but the description does not compensate for the coverage gap or clarify the request body 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?

The description only restates the tool name: "Update a Volume" followed by "Updates the Volume properties." It does not identify which properties can be updated, so it adds almost no specificity beyond the tool name.

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?

There is no guidance on when to use this tool versus sibling volume actions such as resize, attach, detach, or change protection. It gives neither prerequisites nor exclusions.

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