delete_private_network

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

Annotations already declare destructive=true, idempotent=true, and openWorld=true, so the safety profile is covered. The description adds important non-annotation context: deleting the network automatically unassigns all instances from it.

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 operation is front-loaded and appropriately short. There is mild redundancy in repeating 'Delete existing ... by id' for both Private Network and Virtual Private Cloud, but the second sentence contributes the key side effect.

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 delete tool with rich annotations and fully described parameters, this is mostly complete: it names the resource, id-based targeting, and the automatic instance unassignment. It could still mention prerequisites or irreversibility, but annotations cover much of that ground.

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 the schema already documents privateNetworkId and x-trace-id. The description only repeats that deletion is by id, adding no format, constraints, or parameter behavior beyond the schema.

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 states a specific verb and resource: delete a Private Network by id, and includes the underlying DELETE endpoint. It is clearly distinguishable from sibling retrieve/create/patch private-network tools.

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?

It says to delete an existing Private Network by id but gives no explicit when-to-use guidance, no alternatives, and no prerequisites such as verifying the network before deletion.

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