timeweb_delete_balancer

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

Since no annotations are provided, the description bears the full burden of behavioral disclosure. It does disclose the destructive and irreversible nature ('permanently'), which is a key behavioral trait. However, it omits other potential effects such as what happens to associated resources (e.g., rules) or whether the operation is synchronous.

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 a single, front-loaded sentence that conveys the essential action without any fluff or repetition. It is concise and all words carry meaning.

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?

The tool has a simple parameter set with full schema coverage, but no annotations or output schema exist. The description covers the core action and permanence, yet lacks detail about expected response, side effects, or operational context. It is minimally viable but leaves gaps that could confuse an agent.

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 input schema provides complete descriptions for both parameters (balancer_id and format), yielding 100% schema coverage. The description adds no additional meaning beyond what the schema already states, so the baseline of 3 applies.

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 explicitly states a specific verb ('Delete') and a specific resource ('load balancer') with a clear qualifier ('permanently'), making the action unambiguous. It distinguishes itself from related sibling tools like get_balancer or update_balancer, and the resource type is clear.

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, prerequisites, or alternatives. There is no mention of the need to delete balancer rules first or any context about when deletion is appropriate. It simply states the action without any usage context.

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