hcloud_network_delete_route_action

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: a concurrent change on the Network causes a `conflict` error response, telling the agent to expect and handle a specific failure mode.

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?

Short and front-loaded: the action is stated in the first line before the conflict caveat. The Markdown anchor links to #tag/networks are noise that adds no meaning but costs little.

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 mutation with no output schema, the description covers the conflict case but says nothing about the action object that is returned or what state the Network is left in after deletion. The `wait` parameter hints at async behavior, but the description does not build on that.

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 sits at 67% and the nested body fields (destination, gateway) are documented in exceptional detail in the schema itself, including constraints and exclusions. The description adds nothing about `id`, `body`, or `wait`, so it neither compensates for nor improves on what the schema already provides.

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 specific verb+resource ('Delete a route from a Network'), which cleanly separates it from hcloud_network_delete_subnet_action and hcloud_network_add_route_action without needing to name them. The scope is unambiguous, though no sibling is referenced 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?

The description never says when to reach for this tool versus its siblings (delete_subnet, add_route, update_network), nor does it state prerequisites such as the route having to exist. The only guidance is the conflict condition, which is behavioral rather than selection guidance.

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