hcloud_create_floating_ip

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

Annotations already declare write behavior (readOnlyHint=false), non-destructiveness, and open-world scope. The description adds lifecycle context: assignment can happen later and routing is optimized in the home location. It omits cost, quota, idempotency, and failure behavior.

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 purpose is front-loaded, but the opening 'Create a Floating IP' is repeated as 'Create a [Floating IP]' and the many long markdown links make it noisier than needed. The substantive guidance is still reasonably compact.

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 creation tool with a nested body and no output schema, the description covers the core assignment model but leaves out the required `type` choice and wait behavior. Annotations cover safety, but an agent still needs the schema for key creation decisions.

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 description adds meaning for `server` and `home_location`, including later assignment and routing implications. It never mentions the required `type` enum or `wait`, so it only partially compensates for the 50% schema description coverage.

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?

States 'Create a Floating IP' with a specific verb and resource, so the operation is immediately identifiable. It does not explicitly distinguish itself from siblings such as hcloud_create_primary_ip or hcloud_update_floating_ip.

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?

Explains conditional use of `server` versus `home_location` and notes that later assignment is possible, which gives some contextual guidance. It does not state when to choose floating IP creation over alternatives like primary IP creation, nor any exclusions.

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