Add network load balancer member

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

Annotation hints cover the safety profile (readOnly=false, idempotent=true, destructive=false, openWorld=true), and the description goes well beyond them: required scopes (networking:read/manage, not granted by full/read defaults), ownership and 2FA lock enforcement, the fact that acceptance means pending rather than connectivity, the polling contract (in_progress, next_check_seconds, reason_kind waiting vs failure), and explicit idempotency recovery rules (reuse the original key and unchanged request, never auto-retry). This is exactly the behavioral context an agent needs for a risky async mutation.

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 and prerequisites are front-loaded and there is essentially no filler; every clause maps to a real constraint (permissions, approval, async semantics, idempotency recovery). It reads as one very dense block, and fragments like 'Preserve reason_code.' hurt scannability, keeping it from a 5.

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 5-parameter async mutation with no output schema, the description covers everything the agent needs: auth scope, approval workflow, non-destructive-but-pending semantics, how to interpret operation state, and how to behave under transport uncertainty. Nothing material is left to inference.

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 60%, so the schema carries most parameter documentation. The description adds meaning only for idempotencyKey (preserve the original key and unchanged body on uncertain recovery) and obliquely for address ('private server address', validated for network membership). It says nothing about how listener_id and load_balancer_id relate, so it does not compensate for the coverage gap.

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 gives a specific verb (add) plus resource (attached private server address on the selected listener) and adds a scoping constraint: the backend validates membership in this network. An agent can distinguish it from add_network_load_balancer_listener and remove_network_load_balancer_member by name alone. It stops short of explicitly differentiating itself from sibling tools, so 4 rather than 5.

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?

It states concrete preconditions: read current capabilities and owned resource state first, and obtain approval for the exact change. It also implies the required permission scope, which effectively gates when the call can succeed. It does not, however, name an alternative tool or an explicit when-not-to-use condition.

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