iaas_delete_load_balancer

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that — no note about what happens to attached virtual servers, whether the delete succeeds asynchronously, or the consequences and cautions around force deletion.

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?

Three lines where one would do: the first and second lines are the same statement repeated, and the third is a raw endpoint path already captured in the annotation title. Short, but redundancy rather than density.

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 destructive, open-world mutation with no output schema, the description should explain outcome, async behavior, and risk of the forceDelete path. It explains none of these, leaving the agent dependent entirely on annotations plus schema prose.

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 description coverage is 100% and each parameter (id, apiVersion, forceDelete) is documented in the schema, so baseline 3 applies. The description's 'with a given id' merely restates the required parameter and adds no semantics about apiVersion defaults or when forceDelete should be chosen.

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 does convey verb and resource ('Delete load balancer ... with a given id'), but it says the same thing twice and the third line is just the REST path. It offers no differentiation from close siblings such as iaas_delete_load_balancer_operation, iaas_scale_load_balancer, or iaas_create_load_balancer.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites (load balancer must exist, be detached, or be in a deletable state), and no pointer to iaas_delete_load_balancer_operation for async tracking. The agent must infer everything from the name and annotations.

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