hcloud_floating_ip_assign_action

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds the specific failure mode ('422 floating_ip_assigned'), but says nothing about the resulting async action, the `wait` polling behavior, or whether reassignment disrupts existing traffic.

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 core action and short overall, but the title is duplicated verbatim as the first sentence and the markdown link/table formatting is carried over from the API reference rather than written for an agent. Every sentence earns its place, though the styling does not.

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 mutating, open-world action with no output schema and a nested body, the description omits the async action semantics, the wait/timeout behavior, and the preconditions that make the 422 error occur. Adequate to attempt the call, incomplete for anticipating the result.

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?

At 67% schema coverage the description should compensate, but it adds nothing about `id`, `body.server` or `wait` beyond what the schema already says. The `wait` parameter's default polling behavior, the most consequential knob, is left entirely to the schema text.

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 opening line states a specific verb and resource ('Assign a Floating IP to a Server'), which is unambiguous and clearly the inverse of the sibling hcloud_floating_ip_unassign_action. It doesn't explicitly name or contrast with that sibling, but the operation is clear enough to select without opening the schema.

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?

No guidance on when to use this versus hcloud_floating_ip_unassign_action or hcloud_update_floating_ip, and no prerequisites are stated (e.g. the IP must be unassigned, server residency constraints). The only hint is the 422 'floating_ip_assigned' error row, which implies a precondition rather than stating one.

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