vsz_delete_ap

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 merely restates the action implied by the name ('remove') and does not mention side effects, reversibility, prerequisites, or what happens to the AP after removal, leaving significant behavioral gaps.

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 exceptionally concise: a single clear sentence followed by a compact Args block that exposes both parameters. Every word earns its place, with no filler or repetition.

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 two-parameter operation, the description covers the core purpose and parameter meanings, and an output schema exists so return values need not be described. However, it omits usage guidelines and behavioral effects, which are crucial for a mutation tool lacking annotations, leaving the description minimally complete.

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 zero descriptions for its two parameters, but the description's Args section compensates by defining host as 'vSZ controller IP or hostname' and ap_mac as 'AP MAC address'. This adds meaningful semantics beyond the schema's basic type and title.

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 states 'Remove an access point from vSZ management' with a clear verb and resource, making the tool's purpose unambiguous. It also distinguishes it from sibling delete tools like vsz_delete_zone and vsz_delete_wlan by specifying 'access point'.

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, nor any exclusions or prerequisites. It only describes the action itself without contextualizing its appropriate use among the many sibling operations.

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