unifi_get_acl_rule_ordering

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

No annotations provided, and the description merely states 'Get' implying read-only, but fails to disclose any behavioral traits such as whether it is a safe read, requires authentication, or has rate limits.

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?

Extremely concise at 5 words, front-loaded with verb and resource. No wasted words.

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 zero-parameter read tool, the description is minimally adequate. However, it lacks context on what 'ACL rule evaluation ordering' means or what the response contains, leaving room for ambiguity.

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?

Zero parameters, schema coverage 100%. Baseline score of 3 applies as description adds no parameter info, but none is needed.

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 'Get ACL rule evaluation ordering' is specific: verb 'Get' and resource 'ACL rule evaluation ordering'. It clearly distinguishes from sibling tools like unifi_get_acl_rule (gets a specific rule) and unifi_list_acl_rules (lists rules).

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 explicit guidance on when to use this tool versus alternatives. Given sibling tools, it would benefit from stating that this is for retrieving the ordering, while other tools handle individual rules or lists.

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