get_load_balancer_pools

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

With no annotations, the description fully carries behavioral disclosure. It details that the tool lists pools, shows protocols, algorithms, members with status, and health monitor associations, and returns JSON. No contradictions.

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?

Description is well-structured with a summary line, bullet list of functions, usage examples, args, and returns. It is concise without unnecessary repetition, though slightly verbose in listing functions.

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?

Given the simple tool with 1 optional parameter and an output schema existing, the description covers purpose, behavior, parameter meaning, and return format comprehensively. No gaps.

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 has 0% description coverage, but description adds meaning: 'Optional listener name or ID to filter pools'. However, it lacks format details or examples that would further clarify usage, 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?

Description clearly states it gets load balancer pools, optionally filtered by listener. It explicitly lists functions like listing pools, showing protocols, members, and health monitors, distinguishing it from sibling tools such as get_load_balancer_list or get_load_balancer_pool_members.

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?

Description provides explicit usage examples like 'Show all load balancer pools' and 'List pools for listener [name/id]', guiding when to use. However, it does not mention alternatives or when not to use this tool despite ample sibling tools.

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