unifi_update_port_forward

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Update a port forwarding rule by its _id.' It does not disclose idempotency, error behaviors (e.g., what if rule not found), authentication needs, or side effects. This is insufficient for a mutation tool.

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 very short (one sentence), which is concise but lacks substance. It does not earn its place because it fails to provide necessary context. While it is not verbose, the under-specification makes it less effective.

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?

Given the complexity (7 parameters, mutation tool, no output schema), the description is severely lacking. It only identifies the primary key parameter. There is no info on return values, error states, or usage context. The tool cannot be used effectively with this description alone.

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% (no parameter descriptions), and the tool description only mentions the _id parameter. It does not explain the meaning or usage of the other 6 optional parameters (enabled, fwd, fwd_port, src_port, name). The description adds no value beyond the schema's parameter names.

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 tool updates a port forwarding rule identified by '_id'. The verb 'update' and resource 'port forward' are specific. However, it does not distinguish from sibling tools like 'create_port_forward' or 'delete_port_forward', but the action is unambiguous.

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 vs alternatives. It does not mention prerequisites, whether the rule must exist, or when to use create/update/delete. The description only states what it does, leaving the agent to infer usage context.

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