unifi_gen_createaclrule

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

Annotations already flag this as destructive, non-idempotent and open-world, so the safety profile is known. The description adds nothing beyond that — it does not surface the confirm/dry_run gating, ordering/index side effects, or what happens to existing rules, all of which are meaningful for a destructive create.

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?

Single short sentence with zero padding, which is good, but it is under-specified rather than concise in a useful sense; the doc-page attribution consumes half the description's limited real estate.

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 create operation with no output schema, the description should at least note that a confirm token is required to actually apply, that unconfirmed calls preview, and that rule order/index matters. None of that is present, leaving an agent to discover it only from the 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 description coverage is 100% and the schema documents body/confirm/dry_run including the 'YES to apply' preview semantics. The description contributes no parameter meaning of its own, so baseline 3 applies.

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 says 'Create ACL Rule', which gives a verb and resource, but it is essentially a restatement of the tool name plus a vendor doc URL. It does nothing to distinguish this tool from siblings such as unifi_net_create_acl_rule or unifi_gen_createfirewallpolicy, and never clarifies how an ACL rule differs from a firewall policy/zone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many create_* siblings. The only extra content is a documentation link, which is not usage guidance.

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