lb_resize

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

With no annotations, the description carries the full burden. It only says 'Resize the capacity', leaving out important behavioral traits such as whether the operation is synchronous, requires downtime, or has any other side effects. The agent lacks context for safe invocation.

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 concise, consisting of a one-sentence summary followed by a parameter list. It avoids unnecessary words and is structured clearly. However, it could be more compact by integrating parameter descriptions into prose.

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 has an output schema and 4 required parameters for a state-modifying operation, the description lacks completeness. It does not explain return values, error conditions, or what happens during resizing. More context is needed for an agent to use it safely.

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 0%, so the description must compensate. It lists each parameter with a single-line description (e.g., 'The destination group ID'), but these add minimal meaning beyond the schema property titles. The meaning of 'destination' and 'resource' in the context of resizing is unclear.

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 action ('resize') and the target resource ('load balancer capacity'). It distinguishes the tool from siblings like 'lb_list' and 'lb_reload' by specifying the operation on capacity. However, it could be more precise about what 'capacity' means.

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 or alternatives. There is no mention of prerequisites, potential side effects, or when not to use it. The description solely states the operation.

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