Get network load balancer

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for adding auth requirements (networking:read / networking:manage), ownership and feature-availability enforcement, service 2FA locks, and the readiness caveat about pending or unqualified endpoints. The aside about "networking:manage for changes" on a readOnly tool is slightly misleading but reads as permission-family boilerplate rather than a true contradiction.

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?

Three front-loaded sentences with no filler: scope, readiness caveat, then permissions. "A pending or unqualified public endpoint is not ready" is terse to the point of being slightly opaque, which keeps this 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?

No output schema exists, so the description carries the return-value burden and does so by naming listeners, members, generation and health. Combined with the ownership, 2FA and permission gating, an agent has everything needed to call this correctly.

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 a single parameter and 100% schema description coverage (UUID format, length, pattern all documented in the schema), the baseline of 3 applies. The description adds no format or sourcing detail beyond what the schema already states.

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 ("Read one owned load balancer") and enumerates what the read returns: listeners, members, generation and health. The word "one" plus the singular resource cleanly distinguishes it from the sibling list_network_load_balancers without needing the schema.

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 real context for use: explicit networking:read is required, full/read defaults do not grant networking, and the target must be an owned resource. It does not name the alternative (list_network_load_balancers) or state when-not to use it, so it stops short of explicit routing.

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