network_start

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says the tool starts capture; it does not mention whether capture persists until network_stop, whether results are returned, whether a browser connection is required, or any stateful side effects. This is a meaningful gap for a state-changing tool.

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 a single compact sentence with no filler, and the core action is front-loaded. It is concise and well-structured, even though it leaves important behavioral detail out.

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 stateful operation with no annotations and no output schema, the description is incomplete. It does not explain what the tool returns, when capturing stops, or how this relates to sibling tools like network_stop and network_list. These details matter for correct invocation and interpretation of results.

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 0%, and the description does not mention max_time or include_static at all. An agent must infer that max_time caps capture duration and include_static controls whether static resources are included, which is not reliable enough without explicit documentation.

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 states a specific action (start capturing), a clear resource (HTTP traffic), a target (active tab), and a mechanism (CDP). It is immediately distinct from siblings like network_stop and network_list because it names the initiating role rather than stopping or listing captured traffic.

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?

There is no explicit guidance about when to use this tool versus network_stop, network_list, or network_request. The intended usage is only implied by the verb 'start', and no prerequisites or exclusions are provided.

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