Delete Load Balancer

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

The description adds 'permanently' to confirm irreversibility, but the annotations already set destructiveHint=true and idempotentHint=true. The description does not disclose additional behaviors like side effects on associated resources (e.g., services, targets).

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 concise sentence that communicates the essential action without extra words. It is front-loaded and earns its place.

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 delete tool with one parameter and annotations present, the description is minimally adequate. However, it lacks mention of behavior if the resource does not exist (despite idempotentHint) or any prerequisites (e.g., whether the load balancer must be detached).

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 one parameter 'id' with description 'Resource ID' (100% coverage). The tool description does not elaborate beyond this, so it adds marginal value. Baseline 3 is appropriate given high schema 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?

The description clearly states the action 'delete' and the resource 'load balancer', using the adverb 'permanently' for emphasis. It distinguishes well from sibling delete tools that target different resources (e.g., servers, networks).

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 usage guidance is provided. There is no indication of when to use this tool versus alternatives like hetzner_delete_lb_service or hetzner_detach_lb_from_network, nor any prerequisites or conditions.

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