tailscale_set_log_stream_config

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

Annotations already indicate idempotent and non-destructive behavior. The description adds useful context about per-destination required fields and the prerequisite for S3 role ARN. It does not contradict annotations and provides additional behavioral detail beyond annotations.

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 appropriately sized with two paragraphs. It front-loads the purpose and then provides structured per-destination details. Slightly more could be streamlined, but it is effective and not verbose.

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?

Given the complexity of the tool (14 parameters), the description covers the main use case and conditional requirements. However, it does not explain what the return value is (likely the updated config) or any side effects like overwriting existing config. For a setter with no output schema, this gap reduces completeness.

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%, so baseline is 3. The description adds value by grouping parameters by destination type and specifying required combinations (e.g., url+token for non-s3, bucket+region+authentication for s3), which goes beyond the individual parameter descriptions.

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 the action ('Set the log streaming configuration') and the resource ('for a specific log type'), and distinguishes it from sibling tools like get/delete/list. The verb and resource are specific and unambiguous.

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 implicitly guides usage by listing per-destination required fields and includes a critical prerequisite ('Call tailscale_create_aws_external_id first when using rolearn'). However, it does not explicitly state when to use this tool vs alternatives like get/delete/log stream configs, though the context is clear.

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