zeek_detect_outliers

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states the tool compares activity and flags outliers but does not clarify whether it modifies any data, if authorization is needed, or whether a baseline must be precomputed via “zeek_network_baseline”. More details on potential side effects or dependencies are needed.

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 concise with two sentences, front-loading the core purpose. No extraneous words, but it could better incorporate parameter guidance or output hints without losing brevity.

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 covers the tool's purpose and metrics, but since there is no output schema, it does not explain what the tool returns (e.g., host list, alert details, or counts). For a detection tool, omitting output shape reduces completeness. Parameters are well-covered.

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 description coverage is 100%, and the parameters ‘timeTo’, ‘timeFrom’, and ‘stdDevThreshold’ are already described in the schema. The description mentions “standard deviations from mean” which aligns with ‘stdDevThreshold’, but adds no new meaning beyond what the schema provides. Hence baseline score of 3.

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 that the tool compares current network activity against a baseline and identifies statistical outliers, specifying metrics like byte volumes, connection counts, port diversity, and timing patterns. This distinguishes it from sibling tools such as “zeek_detect_anomalies” or “zeek_detect_beaconing” by focusing on statistical deviation from a baseline.

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 lacks guidance on when to use this tool versus alternatives like “zeek_detect_anomalies” or “zeek_detect_beaconing”. It does not specify prerequisites (e.g., whether a baseline must already exist) or when it should not be used.

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