hcloud_delete_floating_ip

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

Annotations already declare destructive=true and openWorldHint=true, so the description earns credit by adding the temporal unassignment behavior and the exact 422 must_be_unassigned failure condition. That is meaningful behavioral context beyond what the structured annotations provide.

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 content is front-loaded and logically ordered, with the critical caveat placed before the error table. However, 'Delete a Floating IP' and 'Deletes a Floating IP' restate each other, and the repeated markdown anchor links add some visual noise.

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 one-parameter destructive tool with annotations and no output schema, the description covers the main side effect and failure mode sufficiently. An agent has what it needs to call it correctly and interpret the likely error.

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?

There is a single required id parameter and schema description coverage is 100%, so the schema fully documents it. The description adds no additional parameter syntax or meaning, making baseline 3 appropriate.

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 first line and body both state a specific verb ('Delete') and resource ('Floating IP'), which clearly separates it from the many other delete_* siblings by resource. The only weakness is minor restatement between the title-like first line and the body.

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?

It gives the key context for when the call succeeds or fails: an assigned IP is auto-unassigned until 1 May 2026, after which deletion requires unassignment first. It does not explicitly name hcloud_floating_ip_unassign_action as the preferred alternative, so it stops short of full routing guidance.

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