List Load Balancers

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

Annotations already provide readOnly, non-destructive, idempotent hints. The description adds 'list all' which could conflict with openWorldHint (pagination), but not contradictory. No mention of pagination behavior or rate limits beyond schema.

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?

Single sentence, 13 words, front-loaded with verb and scope. No unnecessary words. Efficient.

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 simple tool with complete schema and annotations, description is adequate. Could mention pagination default or result ordering, but not required. Slight gap in clarifying 'list all' vs. paginated results.

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 descriptions cover 100% of parameters. Description restates 'optional filtering by name or labels', adding no new meaning. Baseline of 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 verb (list), resource (load balancers), scope (project), and optional filters. Distinguishes from sibling list tools by resource type and from get_load_balancer (single vs. many).

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?

Implies use when needing multiple load balancers or filtering by name/labels, and implicitly differentiates from get_load_balancer for single retrieval. No explicit when-not or alternatives, but context is clear.

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