hcloud_server_change_alias_ips_action

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

The description discloses the critical destructive behavior that existing alias IPs are replaced, not appended. This is exactly the kind of beyond-annotation context an agent needs for a destructive mutation, and it aligns with destructiveHint=true.

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 description is short, front-loaded, and organized around the operation and its key replacement caveat. Every sentence contributes directly to correct invocation.

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 destructive nested-body action with annotations and no output schema, the description covers the most important behavioral risk: alias replacement. It does not discuss action polling or response shape, but those are partly handled by the wait parameter description in the schema.

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 moderate at 67%, and the description adds essential meaning to the alias_ips parameter by explaining replacement versus addition semantics. The id, network, and wait parameters are largely covered by the schema itself.

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 states a specific verb and resource: changing alias IPs of an already attached Network. It is clear enough to distinguish the operation from attach/detach siblings, though it does not explicitly name any sibling alternative.

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 clear operational guidance: existing aliases are replaced by the request body, so adding an alias requires including all existing aliases plus the new one. It does not explicitly state when to choose this over attach/detach or other network actions.

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