unifi_gen_getaclrulepage

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only provenance ('generated from developer.ui.com/network/v11.0.97/getaclrulepage'), which adds nothing about behavior related to pagination, default return size, or filter semantics.

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?

One short, front-loaded sentence with the action stated first. The trailing provenance URL is of marginal value to an agent but adds little bloat.

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?

There is no output schema, and three parameters are undocumented everywhere. For a paginated list endpoint, an agent needs the filter format and paging defaults, and neither the description nor the schema supplies them.

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 0%: limit, filter, and offset are all undocumented, and the description does not explain the filter string syntax, that limit caps at 200, or the default page size. The single word 'List' implies pagination at most.

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: 'List ACL Rules'. It is clear what the tool returns, but it does not distinguish itself from the sibling unifi_net_list_acl_rules, which appears to serve the same purpose.

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?

No guidance is given about when to use this tool or when to use another tool instead. Given that the sibling list unifi_net_list_acl_rules overlaps, the absence of any routing hint leaves the agent to guess.

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