get_load_balancer_pools

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

Annotation coverage is zero, so the description carries the full burden; it does disclose that results include protocols, algorithms, member statuses, and health monitor associations, and the 'Get/Lists/Shows' framing implies a read-only operation. However, it says nothing about permissions, pagination, or behavior when the listener filter matches nothing.

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 main purpose is front-loaded in the first line and the function bullets are scannable. The four quoted user phrases are somewhat repetitive padding, but each is short and supports retrieval matching.

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 one-parameter read tool with an output schema and full schema coverage, the description covers what is returned at a useful level of detail. Only minor gaps remain (filter-miss behavior, pagination) and are not critical for correct invocation.

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% and the single parameter is already documented as an optional listener name/ID filter. The description's phrase 'optionally filtered by listener' merely restates the schema, so baseline 3 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 (get load balancer pools) plus the filter scope, which is clear and distinct from the sibling get_load_balancer_pool_members. It does not explicitly name that sibling as the alternative for member-only queries, but the primary purpose is unambiguous.

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 'Use when user requests' block with four verbatim example queries gives an agent concrete triggers for selecting this tool. There is no explicit 'do not use when' or named alternative, so it stops short of a 5 despite clear usage context.

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