termix_tailscale_list_tailscale_devicesLists all Tailscale devices in the configured tailnet using the stored API key. Returns device details for fleet management.
List Tailscale devices. Returns the list of devices in the configured tailnet using the stored API key.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry the read-only/idempotent/non-destructive profile. The description adds meaningful context by disclosing that authentication comes from a stored API key and that the operation targets the configured tailnet, making the call's dependencies visible.
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 short sentences front-load the action and then add the key context about tailnet and API key. The first sentence slightly restates the title, but the whole description is efficient.
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 parameterless, annotation-rich read operation, the description is largely complete. It could name the closest sibling or the shape of the returned device list, but those are minor gaps given the simple interface.
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?
With zero parameters and 100% schema coverage, there is nothing for the description to document. The mention of the stored API key usefully explains why no credential parameters are needed.
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?
States exactly what it does with a specific verb ('List') and resource ('Tailscale devices'), plus the scope qualifier 'configured tailnet'. This is distinct from the sibling Tailscale status/IP tools because it targets the device inventory rather than status or connection state.
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?
Implied usage: call this when you need the tailnet device inventory. It notes the auth context (stored API key) but does not explicitly say when to prefer it over similar siblings such as termix_metrics_get_tailscale_status_ips.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.