remove_load_balancer_target

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove' implies a destructive mutation, it doesn't specify whether this requires specific permissions, if the action is reversible, what happens to load balancer traffic during removal, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise - a single sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable at a basic level.

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 destructive mutation tool with 5 parameters (including complex nested objects), 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It provides only basic purpose without addressing behavioral implications, parameter meanings, or expected outcomes, leaving critical gaps for safe and correct tool usage.

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 description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain the 'id' parameter (load balancer ID?), the 'type' enum values, or the nested objects for different target types. With 5 parameters (including complex nested objects) completely undocumented, this creates significant ambiguity for proper tool invocation.

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 ('Remove') and resource ('a target from a load balancer'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'delete_load_balancer_target' (which doesn't exist in the list) or 'delete_load_balancer_service', leaving some ambiguity about 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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, consequences, or relationships with sibling tools like 'add_load_balancer_target' or 'delete_load_balancer', leaving the agent to infer usage context.

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