iaas_delete_network

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — notably it never warns that deletion is irreversible or that forceDelete can desynchronise the cloud provider from Aria Automation, which is the most important behavioural fact here and lives only in the schema parameter text.

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?

It is short, but the first two lines say the same thing twice and the third merely repeats the endpoint already exposed in the annotation title. It is not bloated, but the redundancy means little of the text earns its place.

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, open-world delete operation with no output schema, the description should warn about irreversibility and the forceDelete trade-off. As written, an agent must open the schema to learn the one fact that could prevent a costly mistake.

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%, so the id, apiVersion and forceDelete semantics (including the force-delete caution) are already documented in the schema. The description adds nothing about parameters, which is acceptable at this coverage level but earns no extra credit.

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 and resource ('Delete a network') plus the underlying endpoint DELETE /iaas/api/networks/{id}, so an agent can identify the operation. It does not differentiate itself from near neighbours such as iaas_delete_network_profile or iaas_delete_internal_network_ip_range, which matters in this very large sibling set.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only content is a restatement of the operation and the HTTP path, leaving the agent to infer usage entirely.

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