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

Annotations already establish read-only and open-world behavior, and the description adds useful context: the required permission scope and a detailed preview of returned fields such as DNS IPs, pool targets, listener rule order, and certificates. It does not describe error behavior, but that is minor for a read-only get tool.

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 two compact sentences with the main purpose front-loaded, followed by a tight enumeration of returned fields and the permission scope. Every phrase contributes useful information without repetition.

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?

With no output schema, the description takes on the job of explaining return contents and does so thoroughly: status, IPs, pool/target health details, listener rules, and certificates. The permission scope adds operational context, making the definition complete for a one-parameter read tool.

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 coverage is 100%, and the schema already documents the single "lb" parameter as the load balancer id returned by list or create operations. The description adds no parameter-specific syntax or constraints beyond what the schema provides, so the baseline score 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?

The phrase "One load balancer in full" clearly identifies retrieval of a single load balancer and enumerates the returned data. It distinguishes itself from list-style siblings through "One," but does not explicitly contrast with get_load_balancer_metrics or list_load_balancers.

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 description implies this is for fetching a single load balancer's full configuration, but it gives no explicit when-to-use guidance versus list_load_balancers or get_load_balancer_metrics. The only usage cue is the permission scope "vms.read."

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