Find devices hosting a specific Tailscale service by supplying its name, returning the list of hosts for quick identification.
List devices hosting a specific Tailscale Service.
| Name | Required | Description | Default |
|---|---|---|---|
| serviceName | Yes | The service name |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description restates the purpose without adding behavioral context beyond what annotations provide, such as side effects, response size, or pagination.
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, front-loaded sentence with no filler. Every word is necessary and directly conveys the tool's function.
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?
The description is adequate for a simple list tool with one parameter and rich annotations. However, without an output schema, it could hint at the return format (e.g., a list of device identifiers). Missing this context makes it less complete.
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 'serviceName' described as 'The service name'. The description does not add further meaning (e.g., format, allowed values, or how to obtain the name). 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 'List devices hosting a specific Tailscale Service' clearly states the action (List), resource (devices hosting a service), and specificity (specific Tailscale Service). It distinguishes from siblings like tailscale_list_services which lists services themselves.
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 usage for listing hosts of a service but provides no explicit guidance on when to use this over alternative list tools (e.g., tailscale_list_services) or any preconditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.