hcloud_volume_resize_action

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, and the description restates the growth-only constraint (also implied by the schema). It adds nothing about irreversibility, cost implications, or what happens to the attached server during resize — meaningful gaps for a destructive mutation, but not contradictions.

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, front-loaded with the operation and immediately followed by the key constraint. No padding, though the duplicated title line 'Resize Volume' is redundant with the tool name.

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 an action-triggering mutation with no output schema, the description should say that an async action is returned and that wait controls blocking. It is adequate on what changes but silent on the result and on side effects for a mounted Volume.

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 67% and all three parameters (id, body.size, wait) carry their own descriptions, so the baseline is 3. The description adds no syntax, units, or constraints beyond what the schema already states (size in GB, must exceed current size).

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+resource ('Resize Volume', 'Changes the size of a Volume'), which cleanly distinguishes it from metadata siblings like hcloud_update_volume or hcloud_volume_attach_action. It does not explicitly mention the sibling, but the operation is unambiguous.

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 one clear consumption rule ('downsizing a Volume is not possible'), which tells the agent when not to call it. It offers no alternatives, no prerequisite checks, and no guidance on the async/wait behavior for callers who need the resize to finish.

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