unifi_delete_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 states 'Delete' which implies destructiveness, but it does not disclose consequences such as whether the deletion is permanent, disconnects clients, or requires specific permissions. This is a minimal level of transparency for a destructive operation.

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, concise sentence. It is front-loaded with the verb and resource, with no extraneous words or redundancy. Every word contributes to clarity.

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 one-parameter tool with no annotations or output schema, the description is technically sufficient to state the action, but it lacks critical context for an agent: safety implications, prerequisites, or how to retrieve the WLAN ID. The description is too sparse to be considered complete for safe autonomous invocation.

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?

The schema has no descriptions (0% coverage), so the description must compensate. It does reference 'WLAN ID' which names the parameter, but it does not explain what the ID looks like or how to obtain it. The added meaning is minimal beyond the schema's type and property name.

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: 'Delete a Wi-Fi SSID network by WLAN ID.' It uses a specific verb ('Delete') and resource ('Wi-Fi SSID network'), and the 'by WLAN ID' distinguishes it from other WLAN operations like create, update, or list. This unambiguously identifies the tool's purpose.

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 usage guidance is provided. The description does not mention when to use this vs. alternatives (e.g., using unifi_set_wlan_status to disable rather than delete), nor does it advise obtaining the WLAN ID from unifi_list_wlans. The agent is left without contextual cues for appropriate usage.

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