Get service

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered without description help. The description adds what the response contains (MagicDNS name, virtual IP, configuration), which is useful but no deeper behavioral context such as error handling for an unknown service name.

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?

A single front-loaded sentence with no filler; the returned-fields clause earns its place. It is efficiently sized, though very terse for a tool with a large sibling set.

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 read-only getter with one required param and full annotation coverage, the description is nearly sufficient. With no output schema present, the brief enumeration of returned fields (MagicDNS name, virtual IP, configuration) is a meaningful partial substitute, leaving only error/not-found behavior unaddressed.

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?

There is one parameter with 100% schema description coverage, so the schema already documents serviceName. The description adds nothing about the parameter's format (hostname vs. fully qualified name vs. tag), so the baseline of 3 applies.

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 a specific verb and resource (get details for a specific Tailscale Service) and names the returned content. The word "specific" implicitly distinguishes it from tailscale_list_services, but no sibling is named explicitly, so it stops short of a 5.

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 gives no when-to-use guidance, no prerequisites, and never points to the obvious alternatives (tailscale_list_services to discover names, tailscale_update_service / tailscale_delete_service for mutations). Usage can only be inferred from the required serviceName parameter.

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