hcloud_update_floating_ip

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds no behavioral context whatsoever — it doesn't warn that the labels map replaces the existing set, that the operation overwrites current values, or what a successful response looks like. No contradiction, but zero added value.

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?

Short, but the two sentences are pure duplication — the second adds only a markdown anchor to the first. Brevity here comes from under-specification rather than efficiency.

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 mutation with a nested request body, no output schema, and partial parameter documentation, the description is inadequate. An agent cannot tell what the update affects or what constraints apply without reading the raw 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 description coverage is 50% and the body object itself is undocumented; the description does not mention the id or any updatable field. With a nested FloatingIPUpdateRequest containing name/labels/description, the description should at least signal which fields are mutable, but it contributes nothing beyond the schema.

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 says only 'Update a Floating IP' and then repeats the same statement with a docs anchor link. It restates the tool name rather than explaining what an update can change (name, labels, description) or how it differs from the many sibling update_* tools. An agent learns nothing beyond the name itself.

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 when-to-use guidance, no distinction from siblings such as hcloud_floating_ip_assign_action or hcloud_update_primary_ip, and no prerequisites mentioned. The agent must infer everything from the name.

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