delete_wifi_broadcast

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 'Delete' but does not mention irreversibility, whether associated clients/networks are affected, permission requirements, or any side effects beyond the delete operation itself.

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 short and front-loaded with the core purpose. Parameter explanations are compact and provide maximum useful information with minimal 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 three-parameter delete operation, the description effectively covers all parameter semantics and the source of the key ID. The only gap is the absence of behavioral caveats such as permanence or side effects, which are especially relevant for a destructive action with no annotations.

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 0%, and the description fully compensates by explaining each parameter: host accepts a console name, ID, or composite ID with format details; site accepts a name or ID; broadcast_id is marked REQUIRED with a source instruction to fetch it from list_wifi_broadcasts.

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?

States the specific action and resource: 'Delete a WiFi broadcast SSID.' This clearly distinguishes it from sibling tools like list_wifi_broadcasts, get_wifi_broadcast, create_wifi_broadcast, and update_wifi_broadcast.

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?

Provides clear context for when to use the tool: when deleting a WiFi broadcast. It also gives actionable guidance by instructing the agent to obtain broadcast_id from list_wifi_broadcasts. It does not explicitly mention when not to use it, but the operation is unambiguous.

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