tailscale_get_network_flow_logs

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the tool is safe. The description adds behavioral context by listing the types of data returned (source/destination, timestamps, traffic metadata). 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: first states the action, second describes contents and use case. No wasted words, front-loaded with key information.

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 simple parameters (2 strings) and no output schema, the description is adequate. It explains what data is returned (source/destination, timestamps, metadata) and the use case. Could mention pagination or time range limits, but not critical for a read-only tool.

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 schema documents parameters sufficiently. The description mentions timestamps but does not add significant meaning beyond what the schema provides (e.g., RFC3339 format, required start). 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 tool name and description clearly state the verb 'Get' and the resource 'network flow logs'. The description provides specifics about showing connections between devices with source/destination, timestamps, and metadata, distinguishing it from other tailscale_get_* tools.

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 mentions the tool is useful for security monitoring and debugging connectivity, giving context for when to use it. There are no alternative flow log tools among siblings, so usage is unambiguous.

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