list_network_load_balancers

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return format ('List of network load balancers with their IP addresses and state'), which is helpful, but lacks critical details like pagination behavior, rate limits, authentication requirements, error conditions, or whether the operation is idempotent. For a list operation with zero annotation coverage, this leaves significant gaps.

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 efficiently structured with a clear purpose statement followed by dedicated 'Args' and 'Returns' sections. Every sentence earns its place by providing essential information without redundancy or fluff.

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 list operation with one parameter and no output schema, the description covers the basic purpose, parameter meaning, and return format. However, without annotations, it misses behavioral aspects like pagination or error handling. It's adequate but has clear gaps in operational context.

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?

The description explicitly documents the single parameter ('compartment_id: OCID of the compartment to list network load balancers from'), adding crucial semantic context beyond the schema's bare title ('Compartment Id'). With 0% schema description coverage and only one parameter, this effectively compensates for the schema's lack of documentation.

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 clearly states the specific action ('List all network load balancers') and resource ('in a compartment'), distinguishing it from sibling tools like 'get_network_load_balancer' (singular) and 'list_load_balancers' (different resource type). It precisely defines the scope and target resource.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_network_load_balancer' (for a specific instance) or 'list_load_balancers' (for a different type of load balancer). The description only states what it does, not when it's appropriate relative to other tools.

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