Retrieve detailed information about a specific Tailscale device using its device ID. Get status, addresses, and configuration to troubleshoot or manage your tailnet.
Get detailed information about a specific device by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| deviceId | Yes | The device ID (numeric id or nodeId, NOT the nodeKey) |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description ('Get detailed information') aligns with read-only behavior but adds no additional behavioral context beyond what annotations offer. No contradictions.
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, well-structured sentence with no superfluous information. It front-loads the core action and is immediately understandable.
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 tool is a simple get operation with no output schema, the description conveys the purpose adequately. However, it doesn't hint at the structure of the returned data, which might be helpful for an agent to know what 'detailed information' includes.
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 sole parameter deviceId is fully described in the schema ('The device ID (numeric id or nodeId, NOT the nodeKey)'). The description adds no further clarification, so it meets but does not exceed the schema's coverage.
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 'Get detailed information about a specific device by its ID,' specifying a unique verb-resource combination. Among siblings like list_devices, delete_device, rename_device, this tool is distinct in retrieving detailed info for a single 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 implies use when a device ID is known, but lacks explicit guidance on when to use this tool versus alternatives like tailscale_list_devices or other getters. No exclusions or alternative suggestions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.