Set log stream config

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety posture is covered. The description adds valuable behavioral context about per-destination required fields and the two-step rolearn workflow, though it doesn't describe rate limits, error handling, or how existing configs are replaced.

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 front-loaded with the core action, then uses a compact bulleted breakdown of per-destination requirements. It is efficient for a 14-parameter tool, though the nested bullet could be slightly tightened.

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 high schema coverage and no output schema, the description covers the key conditional parameter combinations and the external-id dependency. It is nearly complete, though it could mention what happens to an existing config when this is called.

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 the baseline is 3, but the description adds meaningful cross-field constraints (which combinations of url/token/s3Bucket/s3Region/s3AuthenticationType/s3RoleArn are required per destinationType) that the schema only partially encodes in individual field notes.

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 states a specific verb (Set) and resource (log streaming configuration) scoped by log type, and it names the destination categories (Axiom, Datadog, Splunk, Elasticsearch, S3). It is clearly distinguishable from sibling tools like tailscale_set_log_stream_config vs. tailscale_get_log_stream_config or tailscale_list_log_stream_configs.

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 concrete per-destination requirements and explicitly routes the agent to tailscale_create_aws_external_id for rolearn auth. It does not, however, state when this tool should be preferred over alternatives or what prerequisites exist before calling it (e.g. whether the destination must already exist).

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