vsz_delete_wlan

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action 'Delete' but does not reveal important traits such as destructive implications, reversibility, authentication requirements, or behavior when the WLAN does not exist. The parameter listing adds no behavioral context beyond names.

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 brief and to the point: a single action sentence followed by a compact Args list. Each sentence serves a purpose, and there is no filler. The structural format is clean and front-loaded, making it easy for an agent to quickly parse the essential information.

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 simple delete operation with an output schema, the description covers the core purpose and all parameters. However, it lacks usage guidance and behavioral transparency, which are important for a mutation tool. The presence of an output schema means return values need not be described, but the overall description leaves gaps in when/how to use it safely.

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 provides no descriptions for the parameters (0% coverage), so the description must compensate. It does so by explaining each parameter: host as 'vSZ controller IP or hostname', zone_id as 'Zone UUID', and wlan_id as 'WLAN UUID'. This adds meaningful semantic meaning beyond the bare schema titles, although it does not cover any constraints or dependencies.

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's function: 'Delete a WLAN from a zone.' This uses a specific verb (delete), identifies the resource (WLAN), and specifies the context (from a zone). It distinguishes itself from sibling tools like vsz_delete_ap and vsz_delete_zone by naming the WLAN resource.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or preferred use cases. The usage is only implied by the action itself, which is not enough to differentiate from other delete operations like vsz_delete_ap or vsz_delete_zone.

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