delete_wlan

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

Beyond the destructiveHint annotation, the description discloses that deletion is immediate and persisted, and that deleting an SSID disconnects its clients. It also explains why confirm=true is mandatory, giving the agent important behavioral context before invocation.

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 tightly organized: a one-line summary, behavior/risk notes, prerequisite guidance, and a clear Args block. Every sentence contributes useful information with no redundancy.

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 destructive delete operation, the description covers the target, the safety flag, the site/device scope, the immediate effect, and the recommended prerereview. No output schema exists, but nothing essential to calling this tool correctly is missing.

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 100%, so the schema already documents all parameters. The description adds value by explaining why confirm is required, emphasizing that wlan accepts an ID or SSID name, and advising review of get_wlans first, which goes slightly beyond the schema text.

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 first sentence states a specific verb ('Delete') and resource ('a wireless network (SSID)'), which clearly distinguishes it from siblings like create_wlan, update_wlan, and get_wlans. The description's scope 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?

The description provides clear operational guidance: it instructs the agent to review get_wlans first, resolve the target by ID or name, and requires confirm=true. It does not explicitly contrast with create_wlan or update_wlan, but the prerequisite and safety-gate context make the appropriate use clear.

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