unifi_update_wlan

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 merely says 'update configuration' without explaining whether unspecified fields are overwritten, whether the WLAN must exist, or whether the operation is reversible. This lack of detail is a significant gap 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 a single sentence, front-loaded with the action and resource, with no wasted words. However, it is extremely terse and could be considered under-specification rather than efficient conciseness.

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 4 parameters, no annotations, no output schema, and overlapping sibling tools, the description is incomplete. It does not describe return values, effects on unlisted fields, or how it differs from unifi_set_wlan_password/status, leaving an agent without sufficient context to select and invoke the tool confidently.

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?

Input schema coverage is 0%, so the description must compensate for the undocumented parameters. It only clarifies that wlan_id is the identifier, leaving name, enabled, and x_passphrase without any added meaning beyond their 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 verb ('Update'), resource ('configuration of an existing Wi-Fi network'), and identifier ('by WLAN ID'). It is specific enough to understand the tool's basic function, but it does not differentiate from overlapping sibling tools like unifi_set_wlan_password or unifi_set_wlan_status, which also modify WLAN settings.

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_wlan, unifi_delete_wlan, unifi_set_wlan_password, or unifi_set_wlan_status. The description implies the WLAN already exists, but there is no explicit context or exclusions.

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