hcloud_network_delete_subnet_action

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuinely useful failure modes (attached-resource blocking, conflict on concurrent changes). It stops short of stating irreversibility or whether the deletion is idempotent, and the polling behavior of `wait` is left to the schema.

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 short sentences, front-loaded with the action and followed by the blocking conditions. The opening summary line and the following sentence are mildly redundant ('Delete a subnet from a Network' / 'Deletes a single subnet entry'), a minor waste of space.

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 but a rich input schema and destructive annotations, the description supplies exactly the missing pieces: preconditions, the conflict failure mode, and scope. Nothing essential to calling this destructive action correctly is absent.

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 67% and the schema already documents `id` (Network ID), `ip_range` (CIDR of the target subnet), and `wait` (poll to completion). The description adds no parameter-level detail beyond that, so the baseline 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?

States a concrete verb and resource: deleting a single subnet entry from a Network, with the API-level anchor to the networks tag. It is distinguishable from hcloud_delete_network (whole network) and hcloud_network_delete_route_action (routes), though it does not name those siblings explicitly.

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?

Gives clear preconditions for use: subnets with attached resources must be detached first, and a conflicting in-flight change on the Network will yield a `conflict` error. It does not point to the alternative tool (e.g. add/detach subnet operations) that an agent should use instead when the precondition fails, leaving that routing to inference.

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