zeek_dns_tunneling_check

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

No annotations provided, so description must fully disclose behavior. It mentions analysis methods but does not state if it is read-only, permissions needed, or what actions are performed. Missing details on whether it returns alerts or modifies state.

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, no wasted words, directly conveys core functionality.

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?

No output schema and limited description; the agent cannot infer what the tool returns (e.g., list of suspicious queries or summary). Missing details on result format or how to interpret outcomes.

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 description adds little beyond parameter names/defaults. The description's mention of 'query entropy' loosely relates to entropyThreshold but provides no additional context for timeTo/timeFrom.

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 it detects DNS tunneling using specific analysis methods (query entropy, subdomain lengths, TXT/NULL volumes), which distinguishes it from siblings like zeek_dns_summary and zeek_detect_anomalies.

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?

No explicit guidance on when to use this tool vs alternatives. Usage is implied for investigating suspicious DNS activity, but lacks context for when to prefer this over other DNS-focused tools.

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