list_nlb_forwarding_rules

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

The readOnlyHint annotation already communicates that this is a safe read operation, lowering the disclosure burden. The description adds no behavioral details beyond the domain (network load balancer) and does not mention pagination, response shape, filter behavior, or whether returning an empty list is possible. It neither contradicts nor meaningfully extends the annotations.

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 one short, front-loaded sentence with no filler, repetition, or digressions. Every word contributes to identifying the tool's purpose.

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 simple read-only list tool, the combination of a clear one-line description, readOnly annotation, and fully self-describing input schema is largely sufficient. The main missing pieces are output shape/pagination guidance and sibling-tool disambiguation, but neither is critical given how narrow and discoverable the operation is.

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 100%, so the schema already documents datacenter_id, network_loadbalancer_id, depth, and filtersincluding the important silent-empty-warning for filters. The tool description adds no parameter-specific meaning beyond what the schema provides.

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 is specific and action-oriented: "List all forwarding rules of a network load balancer" clearly identifies the operation, resource, and scope. It also naturally distinguishes this from sibling list_alb_forwarding_rules since it targets the network load balancer rather than the application load balancer.

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?

The intended use is reasonably inferable from the description and required parameters, but there is no explicit when-to-use or when-not-to-use guidance. It does not mention the alternative list_alb_forwarding_rules or clarify what distinguishes this tool from similar list tools, so the guidance is implied rather than stated.

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