unifi_gen_deleteaclrule

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered, but the description adds nothing on top: it does not say that deletion is permanent, that the confirm/dry_run preview gate exists, or what a preview returns. The only added text is a provenance URL, which carries no behavioral information.

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 and front-loads the operation, but the trailing 'generated from developer.ui.com/.../deleteaclrule' is implementation provenance that consumes space without helping an agent decide or invoke.

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, irreversible delete with no output schema, the description should warn about permanence and explain the safety gate (a preview unless confirm="YES"). None of that is present, leaving the agent to infer the mutation risk purely from annotations and schema.

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%, and the two documented parameters (confirm, dry_run) are described only in the schema, not the description. The required aclRuleId has no description anywhere, and the description does nothing to explain the preview-vs-apply workflow the parameters encode.

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?

It names a verb (Delete) and a resource (ACL Rule), so the basic operation is identifiable. But it is essentially the tool name expanded, and it gives no way to distinguish it from the near-identical sibling unifi_net_delete_acl_rule that appears in the same sibling list.

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 statement of when to use this tool, when not to, or which sibling to prefer for the same operation. The coexistence of unifi_net_delete_acl_rule (and unifi_gen_deletefirewallzone-style equivalents) makes this ambiguity costly.

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