tailscale_log_stream_set

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

With no annotations, the description carries the full burden of disclosing behavior. It correctly indicates this is a mutation action ('Configure', 'Streams logs') and notes the confirm requirement. However, it omits important details such as potential impact on existing streaming setups, whether the change is reversible, or any authorization or rate-limit context. The description is insufficiently transparent for a configuration mutation tool.

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 exceptionally concise, with two sentences that deliver the core message without any filler. It front-loads the purpose and includes a critical usage note. Every sentence earns its place.

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 tool's moderate complexity (4 required parameters, no output schema, no annotations), the description is too brief. It lacks information about the return value, side effects (e.g., replacement of any existing streaming configuration), and error conditions. An agent would need to infer or experiment to understand the full behavior.

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?

The input schema has 100% description coverage for all 4 parameters, so the baseline is 3. The description adds no new semantic information beyond what is already in the schema; it merely repeats the confirm requirement. While it does not degrade understanding, it does not enhance it either.

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 tool's purpose: 'Configure log streaming for the tailnet.' It uses a specific verb ('Configure') and resource ('log streaming'), and the mention of 'Requires confirm: true' adds a crucial constraint. While it doesn't explicitly distinguish from its sibling 'tailscale_log_stream_get', the naming implies the distinction, and the description makes the action 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 implies usage when configuring log streaming and highlights a prerequisite ('Requires confirm: true'), but it provides no guidance on when to use this tool over alternatives (e.g., the get variant) or when not to use it. The context for use is clear but lacks exclusions or comparison to siblings.

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