Delete WireGuard client

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

With the destructiveHint annotation already present, the description adds substantial context: 'irreversible', 'client loses VPN access', 'keys cannot be restored', and the confirm requirement. This fully discloses the consequences of the operation and goes well beyond the annotation's generic destructive flag.

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 two sentences, front-loaded with the core action, and includes only essential details like irreversibility and confirm. It is efficient with no unnecessary filler.

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 deletion tool with full schema documentation and a destructive annotation, the description covers the effect, irreversibility, and operational requirement (confirm=true). No output schema is provided, but return details are not critical for a delete operation.

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 coverage is 100%, and the description adds no new parameter meaning beyond what the schema already documents. The confirm requirement is repeated in the description, but the schema already explains it in detail. The clientId is also sufficiently described in the 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 states 'Permanently delete a WireGuard client' with a specific verb and resource. It clearly distinguishes itself from sibling tools like disable_client by emphasizing irreversibility, making the delete semantics unambiguous.

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 implies use for deletion but does not contrast with alternatives like disable_client or specify when deletion vs. temporary disable is appropriate. It mentions 'Requires confirm=true' as a condition, but provides no explicit when-to-use or when-not-to-use guidance.

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