unifi_gen_deletefirewallpolicy

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true. The description adds nothing beyond a generated-from URL: it does not mention the preview/confirm behavior, irreversibility, or any cascade effects of deletion.

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 single sentence is brief and front-loaded with the action. However, the 'generated from developer.ui.com/...' boilerplate adds no decision value and consumes part of an already sparse description.

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 operation with no output schema, the description should disclose the preview requirement, irreversibility, and the confirm gate. The schema mentions confirm and dry_run, but the description itself provides no operational context.

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 is 67%: confirm and dry_run are documented in the schema, but firewallPolicyId has no description. The tool description adds no semantic meaning to any parameter, so it fails to compensate for the partially undocumented required parameter.

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 Firewall Policy. This is clear enough to distinguish it from list/get/create/update siblings, but it does not differentiate itself from the near-duplicate unifi_net_delete_firewall_policy or explain the uuid requirement.

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 unifi_net_delete_firewall_policy or the broader unifi_net_* family. It also omits prerequisites such as requiring the firewallPolicyId or the confirm='YES' gate, leaving usage entirely to inference from the schema.

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