Permanently remove a user from your Tailscale tailnet. Deletes the user account and all associated devices, an action that cannot be undone.
Delete a user from the tailnet. This is irreversible — the user and all their devices will be removed.
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | The user ID to delete |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveness. Description adds concrete consequences: 'the user and all their devices will be removed', which is valuable beyond annotations.
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?
Two sentences, clearly front-loaded with action and key warning. No superfluous information.
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?
Given simple tool (1 param, no output schema), the description fully covers action, effect, and irreversibility. No gaps for invocation.
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?
Single parameter 'userId' with description in schema. Tool description adds no extra semantic value; coverage is 100%, so baseline applies.
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?
Clearly states the verb 'delete' and specific resource 'user from the tailnet'. Distinguishes from siblings like tailscale_suspend_user by emphasizing irreversibility and removal of devices.
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 explicit guidance on when to use this tool versus alternatives like suspend or update user role. The irreversible note hints at caution but doesn't provide decision context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.