get_network_load_balancer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it retrieves detailed information, implying a read-only operation, but doesn't cover authentication needs, rate limits, error conditions, or what 'detailed information' entails beyond backend sets and listeners. This leaves significant gaps for an agent to understand the tool's behavior.

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 well-structured and concise, with a clear purpose statement followed by Args and Returns sections. Every sentence adds value without redundancy, making it easy to parse and front-loaded with essential information.

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 tool's low complexity (single parameter, no output schema, no annotations), the description is moderately complete. It covers the purpose and parameter semantics adequately but lacks behavioral details like error handling or authentication, and the return value description is vague ('detailed information including backend sets and listeners').

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 adds meaningful context for the single parameter: 'network_load_balancer_id: OCID of the network load balancer to retrieve.' This clarifies that the ID is an OCID (Oracle Cloud Identifier) and its purpose, compensating for the 0% schema description coverage. However, it doesn't provide format examples or validation rules.

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 tool's purpose: 'Get detailed information about a specific network load balancer.' It specifies the verb ('Get') and resource ('network load balancer'), but doesn't explicitly differentiate it from sibling tools like 'get_load_balancer' or 'list_network_load_balancers' beyond the specificity of 'network' in the name.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_load_balancer' (which might be for classic load balancers) or 'list_network_load_balancers' (which lists multiple), nor does it specify prerequisites or exclusions for usage.

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