zeek_detect_anomalies

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

Description conveys the tool is read-only (detects anomalies) but does not disclose other behavioral traits such as permissions, rate limits, or resource consumption. With no annotations, the description carries the full burden.

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?

Single sentence followed by a list of detection types. Extremely concise with no superfluous text.

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?

Description lacks output format details (e.g., alert structure, severity representation) and does not mention prerequisites like available connection logs. Given no output schema, more context is needed.

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 parameters are already documented. Description adds no extra meaning beyond the context of 'connection logs'. Baseline 3 applies.

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?

Description clearly states it runs statistical anomaly detection on connection logs and lists specific anomaly types. However, it does not explicitly differentiate from sibling tools like zeek_detect_beaconing or zeek_detect_outliers.

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?

Implied usage is for detecting anomalies in connection logs, but no explicit guidance on when to use this tool versus alternatives like beaconing detection or outlier detection.

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