cdp_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 details output behavior (JSON file plus requests.jsonl), session scoping, and no count limit, adding meaningful context beyond the schema. Does not mention error handling or performance impact.

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?

Three short sentences, each adding value: what the tool does, where output goes, no count limit, and when to call it. Purpose is front-loaded with no superfluous information.

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 start command, this covers the core aspects: purpose, output destination, session scoping, and ordering. It lacks explicit description of return value and prerequisites, but given the simplicity of a start operation and the absence of an output schema, it is nearly 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?

Schema covers only 40% of parameters; the description partially compensates by clarifying 'dir' as the destination and 'matching request' implying filter parameters. However, method, url_contains, and resource_type are not elaborated, relying on the agent to infer their meaning from names.

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?

Starts with the action verb 'Start network capture for this session,' clearly identifying the tool's function. Distinguishes from siblings like cdp_network_stop and cdp_network_log by focusing on initiating capture and specifying file output.

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?

Provides explicit timing guidance ('Call before navigating if you need the first document request'), indicating when to invoke relative to navigation. Lacks explicit alternatives or when-not-to-use conditions, so not a full 5.

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