tailscale_device_delete

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

With no annotations, the description carries full burden. It discloses that 'confirm: true' is required, which is a key behavioral constraint. However, it does not mention irreversibility, side effects on connected resources, or whether the deletion is immediate or asynchronous. Additional details would improve transparency.

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-loads the main action, and contains no redundant information. Every word contributes to understanding the tool's purpose and a critical requirement.

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 destructive operation with two required parameters and no output schema, the description covers the basic purpose and a key requirement. However, it omits information about the success/failure response, error handling, or any recovery options, leaving the agent potentially underinformed.

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 100%, so baseline is 3. The description adds the phrase 'Requires confirm: true' which reinforces the schema but provides little extra meaning beyond the parameter descriptions already present. The description does not expand on deviceId usage.

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 a device from the tailnet') and the consequence ('removes the device and revokes its access'), distinguishing it from sibling tools like tailscale_device_get or tailscale_device_rename, which perform different operations on 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?

The description provides no guidance on when to use this tool versus alternatives (e.g., tailscale_device_expire or tailscale_device_authorize). It does not specify prerequisites, such as requiring the device to be online or warnings about irreversible deletion.

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