delete_site_to_site_tunnel

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly states 'permanently removes the tunnel config,' which is a critical transparency point for a destructive action. It does not cover every side effect (e.g., impact on active VPN traffic), but the permanent irreversibility is well conveyed.

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 compact and front-loaded: the primary action and object are in the first sentence, followed by a clear parameter list. No filler or redundant wording; every sentence earns its place.

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 tool, this description is complete: it identifies the action, the irreversibility, and all three required parameters with enough semantic detail. The presence of an output schema means return value explanation is unnecessary, and the description provides what an agent needs to call the tool correctly.

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%, so the description must explain all parameters, and it does: host, site, and tunnel_id each get a concise meaning, including useful format details like 'composite ID (MAC:numericId format)' and 'site name or ID.' This goes well beyond the bare schema.

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 specific verb ('Delete'), resource ('site-to-site VPN tunnel'), and identifier ('by ID'), making the tool's purpose immediately obvious. It also adds 'permanently removes the tunnel config,' which reinforces that this is a destructive delete operation distinct from list/create/update siblings.

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 context: use this tool when you need to permanently delete a site-to-site VPN tunnel. It does not explicitly mention alternatives like update_site_to_site_tunnel, but the delete purpose is unambiguous and no exclusions or prerequisites are needed.

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