zeek_investigate_uid

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

No annotations provided. The description indicates a read operation across multiple logs but does not disclose side effects, auth requirements, or return format. For a read-only tool, this is adequate but lacks explicit safety guarantees.

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?

A single sentence that is front-loaded with the action and resource. No unnecessary words.

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?

The description lacks output schema and does not specify the format of the reconstructed session lifecycle. For a simple tool it is functional but incomplete without return value details.

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% with a clear description for 'uid'. The tool description rephrases 'Follow a specific connection UID' but adds no new semantic details beyond the schema, such as format or validation.

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 verb 'Follow' and specifies the resource 'specific connection UID across all Zeek log types', with the goal 'reconstruct the complete session lifecycle'. This distinguishes it from siblings like zeek_investigate_host which focuses on hosts.

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 use when you have a UID and want full session reconstruction. However, it does not explicitly state when not to use or compare to alternatives like zeek_query_connections.

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