zeek_query_http

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

With no annotations, the description carries the full burden. It discloses supported operations (wildcard, filtering) but does not explicitly state read-only behavior, rate limits, or any side effects. The transparency is adequate but not comprehensive.

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, no filler, front-loaded with core purpose. Every word adds value. Highly efficient for an agent to parse quickly.

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?

For a tool with 10 parameters and no output schema, the description is brief. It covers key features but lacks details on response format, pagination, or integration with other Zeek tools. Sufficient for basic understanding but incomplete for complex use cases.

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% (baseline 3). The description adds context by explicitly mentioning wildcard matching on host/URI, user agent filtering, and status code filtering, which are not fully detailed in schema descriptions. This enhances parameter understanding beyond the schema.

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 'Search Zeek HTTP request logs', which is a specific verb (Search) and resource (HTTP request logs). It distinguishes itself from sibling tools like zeek_query_connections or zeek_suspicious_http by focusing on general HTTP log querying. The additional mention of filtering capabilities reinforces its purpose.

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 guidance on when to use this tool versus alternatives (e.g., zeek_suspicious_http for anomalies). No context about prerequisites or order of operations. The description is functional but lacks explicit usage direction.

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