Delete Floating IP

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

Annotations already indicate destructiveHint=true. The description adds a key behavioral constraint: the API requires the IP to be unassigned since 2026-05-01. This goes beyond annotations by providing a temporal rule and error condition, helping the agent avoid failures.

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?

Two sentences with no wasted words. The first sentence states the action, the second adds a critical constraint. Every word contributes to the tool's understanding.

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 simple destructive operation with one parameter, the description covers the essential purpose and a vital precondition. No output schema is needed for a delete operation. The description is complete enough for an agent to use the tool correctly.

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?

The input schema has 100% coverage with a single parameter 'id' described as 'Floating IP ID'. The description does not add any additional semantic detail about the parameter itself. Baseline score of 3 is appropriate since schema covers it fully.

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 clearly states 'Delete a floating IP permanently,' which is a specific verb-resource combination. It distinguishes itself from sibling tools like hetzner_delete_firewall or hetzner_delete_certificate by focusing on floating IPs. The added detail about the unassignment requirement further clarifies scope.

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 explicitly states that the floating IP must be unassigned first, providing a crucial precondition. It also mentions the error code (must_be_unassigned) for feedback. While it does not name the alternative tool (hetzner_unassign_floating_ip), the guidance is clear enough for an agent to infer the correct sequence.

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