Remove a device's access to your tailnet immediately by deauthorizing it. Reauthorize the device later to restore its connection.
Deauthorize a device, immediately removing its access to the tailnet. The device will need to be re-authorized to reconnect.
| Name | Required | Description | Default |
|---|---|---|---|
| deviceId | Yes | The device ID to deauthorize |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already include destructiveHint: true and idempotentHint: true. The description adds behavioral context: 'immediately removing its access' and the need for re-authorization, which goes beyond the annotations. No contradiction with 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, no fluff. Every sentence provides necessary information without redundancy.
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 the simple tool (1 parameter, no output schema) and comprehensive annotations, the description fully covers the tool's purpose and effect. It is complete enough for an agent to invoke 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 coverage is 100% with a single parameter deviceId described as 'The device ID to deauthorize.' The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.
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 explicitly states 'Deauthorize a device, immediately removing its access to the tailnet', which is a specific verb+resource. It clearly distinguishes from sibling tools like authorize_device and delete_device.
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: 'immediately removing its access to the tailnet' and 'The device will need to be re-authorized to reconnect.' This implies when to use it (to revoke access) and hints at the consequence, though it does not explicitly list when not to use or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.