lb_get

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

With no annotations, the description carries the behavioral transparency burden. It communicates that this is a retrieval operation via 'Get' and indicates a return value, but it does not disclose error behavior, authentication requirements, or explicitly guarantee non-mutation beyond the conventional meaning of 'get.'

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 short, front-loaded, and organized with Args and Returns sections. The Returns line is somewhat redundant with the first sentence, but it is not bloated or filled with filler.

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 single-parameter get operation with an output schema present, the description sufficiently covers the target resource and identifier format. It does not discuss not-found behavior or permissions, but these are less critical for tool selection and invocation, and the output schema can cover return shape.

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 schema only declares a string parameter, while the description adds that the value can be an ID or label and gives concrete examples like 'web-lb' or a UUID. This materially improves the agent's ability to populate the parameter correctly.

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 states a clear verb and resource: 'Get detailed information about a specific load balancer.' It distinguishes itself from sibling tools that target sub-resources like forwarding rules or health status, though it does not explicitly name those alternatives.

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 given for when to use this tool versus lb_get_forwarding_rule, lb_get_health_status, or lb_get_configuration_summary. The description only implies usage when a specific load balancer ID is known, without stating exclusions or alternatives.

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