Remove Load Balancer Target

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

Annotations already declare destructiveHint: true and idempotentHint: true. The description adds no extra behavioral context, such as reversibility or side effects. It only repeats the basic action.

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, which is concise but overly brief for a tool with 5 parameters and nested objects. It lacks structure and front-loads only the action, not the key contextual details.

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?

Given the complexity (destructive action, nested parameters, no output schema), the description is incomplete. It fails to explain parameter relationships, required fields based on type, or what happens after removal.

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?

With 100% schema coverage, the baseline is 3. The description does not add any parameter-specific guidance beyond what the schema provides, such as explaining the role of 'id' or how 'type' interacts with nested objects.

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 states 'Remove a target from a load balancer,' which clearly identifies the action and resource. It distinguishes from the sibling 'hetzner_add_lb_target'. However, it does not clarify what the required 'id' parameter represents (e.g., target ID or load balancer ID), slightly reducing clarity.

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 like 'hetzner_add_lb_target' or other remove tools. There is no mention of prerequisites, when-not to use, or context about target existence.

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