Remove network load balancer member

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

Goes well beyond the annotations (destructive, idempotent, non-readonly): it specifies required scopes (networking:read vs networking:manage, with full/read defaults excluded), backend enforcement of ownership/feature availability/2FA locks, and the full async contract — accepted op is pending, poll next_check_seconds, interpret reason_kind and in_progress, preserve reason_code, reuse the original idempotency key on uncertainty. This is exactly the destructive/mutating context annotations cannot convey.

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?

Purpose is front-loaded and every sentence carries operational content (permissions, enforcement, approval, async polling, retry policy). It is dense and run-on across several clauses, which taxes readability, but there is little true filler.

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, async, no-output-schema mutation with 4 required params, the description supplies scopes, approval requirement, polling semantics, failure interpretation, and recovery rules. Nothing material an agent needs before invoking is missing.

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 coverage is 75% and already documents member_id, load_balancer_id, and idempotencyKey semantics. The description reinforces the idempotency-key preservation rule and references the generation, but adds little concrete syntax or format beyond the schema; a 3 baseline is appropriate.

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 a specific verb and resource: 'Remove a member from rotation using the load balancer generation.' This clearly distinguishes it from add_network_load_balancer_member and remove_network_load_balancer_listener. It does not explicitly name those siblings, keeping it just short of the top band.

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?

Gives concrete operating context: read current capabilities and owned resource state first, obtain approval for the exact change, then poll the operation. It also says never to retry automatically, which is a real don't-do. It lacks an explicit when-to-use-this-vs-alternative routing statement.

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