cloud_delete_network

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

No annotations are provided; the description adds that subnets are removed, which is a key behavioral detail. However, it does not disclose other consequences like impact on attached servers or floating IPs, leaving gaps.

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 description is a single, front-loaded sentence with no unnecessary words, efficiently conveying the action and a 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?

The description covers the core delete action and subnet removal but omits important context like safety checks (e.g., servers still attached), return value (despite output schema), or irreversibility. Moderately complete for a simple tool.

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?

The sole parameter 'network_id' is not elaborated; the description adds no meaning beyond the schema. With 0% schema description coverage, the description should compensate but fails to explain what network_id is or how to obtain it.

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 clearly states 'Delete a network' and notes the side effect of removing attached subnets, distinguishing it from sibling tools like cloud_create_network or cloud_delete_network_subnet.

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 implies when to use (to delete a network) but provides no explicit guidance on prerequisites, such as detaching servers first, or when not to use it.

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