List network load balancers

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds genuinely non-obvious context: that the general full/read defaults do NOT grant networking access, and that ownership, feature availability and 2FA locks are enforced backend-side. The mention of 'networking:manage for changes' is slightly confusing on a read-only tool but signals family-level auth.

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 sentences, all front-loaded: what it returns, then the auth prerequisite, then backend enforcement. Each sentence carries information, though the permission clause is denser than needed for a read-only list call.

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?

There is no output schema, so the description carries the return-shape burden, and it does hint at the payload ('customer-safe health/qualification state'). For a zero-parameter, read-only list tool with full annotation coverage, this is close to sufficient.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter syntax the description could usefully add. The description correctly avoids inventing filter arguments.

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+resource ('List private and public load balancers') and adds the return scope ('customer-safe health/qualification state'), which is more than the title repeats. It does not explicitly distinguish itself from the singular get_network_load_balancer or list_network_appliances, so it stops short of full sibling differentiation.

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 clarifies the permission needed ('networking:read for reads', 'networking:manage for changes') but never says when to choose this over get_network_load_balancer for a single item or list_network_appliances for a different resource. Usage is implied by the name rather than routed explicitly.

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