tailscale_get_audit_log

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

Description adds behavioral detail ('Shows who changed what and when') beyond annotations, which already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. 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?

Two sentences with no redundancy, directly and efficiently conveying purpose and value.

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?

No output schema exists, and description only vaguely states output contains 'who changed what and when'; lacks details on structure, pagination, or error conditions.

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% (start, end described), so description adds no extra parameter meaning; 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 clearly states 'Get the tailnet audit/configuration log' with verb and resource, and distinguishes from sibling tools (e.g., tailscale_get_network_flow_logs) by specifying 'audit/configuration'.

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 via 'useful for troubleshooting and compliance', but no explicit when-to-use vs when-not-to-use or alternative tools are mentioned.

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