hcloud_floating_ip_unassign_action

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

Annotations already declare destructiveHint=true, so the bar is lower; the description earns credit by stating the concrete consequence ('Results in the IP being unreachable') and that reassignment remains possible. It omits what happens if the IP is not currently assigned and whether it fails or is a no-op.

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 and front-loaded with the action and its effect. There is minor redundancy between the heading 'Unassign a Floating IP' and the body 'Unassigns a Floating IP.'

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?

With no output schema and annotations covering destructiveness, the description is largely sufficient but leaves gaps on preconditions (must the IP be assigned?) and on whether an action object is returned for polling via `wait` or hcloud_wait_action.

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 100%, with both the floating IP id and the `wait` polling flag documented in the schema, so baseline 3 applies. The description adds no further semantics about either parameter.

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 names a specific verb and resource ('Unassign a Floating IP') and its behavior contrasts implicitly with the assign sibling. It does not explicitly name hcloud_floating_ip_assign_action as the counterpart, 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?

Usage is implied rather than stated: the note 'Can be assigned to another resource again' suggests the purpose is to free the IP for reassignment, but there is no explicit when-to-use/when-not guidance, no mention of preconditions, and no named alternative tool.

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