unifi_gen_deletenetwork

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the description adds little behavioral context beyond restating deletion. It does not explain force semantics, confirmation behavior, or what dry_run previews beyond what is already present in 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?

The description is very short and front-loads the operation, but the source URL provenance does not help an agent invoke the tool correctly. Its brevity reflects under-specification more than effective conciseness.

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 deletion tool with four parameters and no output schema, the description is insufficient. It does not distinguish this generated variant from the sibling delete tool or explain the force/confirmation/preview interactions that matter for safe invocation.

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 description does not mention any parameters, so it cannot compensate for the 50% schema description coverage. The schema covers confirm and dry_run, and networkId has format validation, but force remains undocumented and the description adds no semantic value.

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: deleting a network. It is clear but does not differentiate this generated tool from the closely named sibling unifi_net_delete_network.

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 provides no guidance on when to use this tool versus alternatives such as unifi_net_delete_network. It also does not mention prerequisites, when deletion is appropriate, or how force/preview behavior should affect usage.

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