Attach Load Balancer to Network

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

The description merely restates the action without disclosing behavioral traits such as idempotency, whether it overwrites existing network attachments, or any effects on the load balancer's public interface. Annotations indicate it is a write operation but not destructive, yet no additional context is given.

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 description is a single sentence with no unnecessary words, front-loading the key action and resources.

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?

The description lacks context about side effects (e.g., whether attaching replaces an existing network attachment, if the load balancer must be in a certain state) and does not reference the output or limitations. For a simple mutation tool with no output schema, more behavioral context is needed.

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 descriptions already fully define all parameters (id, network, ip, ip_range) with clear meanings. The description adds no additional value beyond the schema, so baseline score of 3 applies.

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 the action (attach) and the resources involved (load balancer to a network). It is specific enough to distinguish from siblings like hetzner_detach_lb_from_network and hetzner_attach_server_to_network.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites (e.g., load balancer and network must exist), or whether the load balancer must not already be attached to a network.

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