Delete VPN client

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

The annotations already indicate destructiveHint=true, and the description adds no extra behavioral context beyond the literal 'Delete'. It does not disclose permanence, side effects, permissions, or any irreversibility, which is expected for a delete operation.

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 a single, front-loaded sentence with no fluff. It is concise but lacks valuable context, so it earns points for structure but not content.

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-by-id tool with destructive annotation, the description is minimally viable. However, it omits important contextual details such as scope (user vs org), side effects, and usage prerequisites, leaving the agent to infer too much.

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 parameter description (coverage 0%), and the description only mentions 'by id' without further elaboration. It does not explain where to obtain the client_id, its format, or any constraints beyond the schema's minLength=1.

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 action ('Delete') and resource ('VPN client') with the method ('by id'). It distinguishes from sibling create/list tools, but does not specify whether this targets a user-level or org-level client, which is a potential ambiguity given the sibling org_vpn_client_* tools.

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?

No guidance is provided on when to use this tool versus alternatives, nor any cautionary notes about the destructive nature. The description simply restates the action without contextual instructions.

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