Delete Load Balancer Service

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds no new behavioral context (e.g., prerequisites, error handling, state changes). Bare minimum, does not contradict annotations.

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?

Extremely concise (12 words), single sentence with verb front-loaded. No unnecessary text.

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?

With no output schema, the description does not mention return values or side effects. For a simple delete operation, this may be adequate but lacks context on success/failure behavior. Siblings similarly brief; still room for improvement.

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 100% with descriptions for both id and listen_port. The description reiterates the listen port as identifier but adds little beyond what the schema provides. Meets baseline for full coverage.

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?

Specific verb 'Remove' and resource 'service from a load balancer', with identification by listen port. Clearly distinguishes from deleting the entire load balancer (sibling hetzner_delete_load_balancer) and updating a service (hetzner_update_lb_service).

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?

Implies usage when needing to remove a service, but no explicit mention of when not to use it or alternatives like hetzner_update_lb_service or hetzner_delete_load_balancer. The context is clear but guidance is minimal.

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