zen_capture_network

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

Describes operations (start/stop/read/clear) and that it uses PerformanceObserver, but lacks details on side effects (e.g., whether 'start' clears previous captures) and does not disclose state persistence or permission requirements. No annotations provided.

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?

Extremely concise: one-line purpose followed by a clear list of parameters with explanations. No wasted words, front-loaded, and easy to parse.

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?

Covers operations and parameters adequately, but missing return format (no output schema) and any details on what data the buffer contains, rate limits, or lifecycle. Adequate but could be more complete.

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?

Adds significant meaning beyond the input schema: explains 'op' values, 'since' filtering logic, and 'tab_id' defaults. With 0% schema description coverage, this is essential and well done.

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 captures network requests via PerformanceObserver, with specific operations (start/stop/read/clear). However, it does not differentiate from sibling tool 'zen_intercept' which might also capture network requests.

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 like 'zen_intercept', nor any prerequisites or when-not-to-use conditions. The description only explains the basic operations without context for selection.

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