unifi_create_port_forward

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that this is a create operation, but fails to mention potential side effects (e.g., whether it overwrites existing rules), required permissions, limits on port ranges, or what happens on success/failure. The agent is left guessing about the tool's real-world impact.

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 description is extremely short, but this is under-specification rather than effective conciseness. It omits all parameter context and guidance, making it nearly as minimal as a tautology. A good concise description should still convey essential usage details, which this lacks.

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?

The tool has 5 parameters with no schema descriptions, no annotations, and no output schema. Given this complexity, the description is completely inadequate—it does not explain parameter semantics, required inputs, potential errors, or expected return values. An agent cannot safely invoke this tool based solely on this description.

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 0%, and the description does not explain any parameters. The parameter names (fwd, fwd_port, dst_port, proto) are cryptic to agents unfamiliar with UniFi networking. Without additional semantic context, the agent cannot reliably map values to fields or understand the distinctions between 'fwd' and 'dst'.

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 clearly states the action (create) and resource (port forwarding rule), making it distinct from sibling tools like unifi_list_port_forwards and unifi_delete_port_forward. However, it does not elaborate on the specific type or scope of port forwarding, leaving some ambiguity about its exact functionality.

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 provided on when to use this tool versus alternatives such as unifi_create_firewall_rule or unifi_create_network. The description does not mention prerequisites, typical use cases, or exclusions, leaving the agent without decision support.

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