unifi_update_wlan

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

No annotations provided, so description carries full burden. It discloses the merge behavior, but does not mention potential side effects (e.g., AP restart, client disconnection) or authorization requirements.

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?

Description is two sentences plus a list of common uses, efficiently front-loading the verb and resource with 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 mutation tool with no annotations, no output schema, and 9 undocumented parameters, the description omits return value, error handling, and complete parameter documentation, making it incomplete.

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%, so description must compensate. It only explains a few parameters (passphrase, enabled, wlan_band, is_guest) in the common uses list, leaving others (hide_ssid, name, vlan_id) undocumented.

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 'Update a WLAN by its _id' and lists common use cases (change password, enable/disable SSID, change band, toggle guest mode), distinguishing it from sibling tools like create, delete, get, and list operations.

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?

The description mentions 'Fetches current config and merges your fields', implying partial updates, but does not explicitly state when to use this tool versus create/delete, or mention prerequisites like ensuring the WLAN exists.

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