tailscale_acl_get

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

Describes return format (JSON) and content (full policy including rules, groups, hosts, tag owners). No annotations provided, so description carries full burden; it adequately discloses the read-only nature but lacks details on authentication or rate limits.

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 sentences, no wasted words. First sentence states action, second clarifies return content. Front-loaded and 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?

Complete for a no-parameter read operation. Specifies what is returned (full policy). Slightly lacking in confirming authentication needs, but acceptable.

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?

No parameters, so schema coverage is 100%. Baseline score of 4 is appropriate; description does not need to add param information.

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?

Clearly states it gets the current ACL policy for the tailnet as JSON, specifying the verb and resource. Distinguishes from sibling tools like tailscale_acl_set or tailscale_acl_preview by focusing on retrieving the current policy.

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?

Implies usage when the current ACL policy is needed. Lacks explicit guidance on when not to use or comparison with siblings, but the context is clear enough for this simple retrieval operation.

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