get_network_log

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

The description indicates a read operation and mentions the optional clear parameter. However, it does not disclose potential side effects of clearing, nor does it address rate limits, size constraints, or session impact. No annotations exist to compensate.

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 concise sentences front-load the action and key benefits. Every word contributes value; no fluff or repetition.

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?

Given no output schema, the description hints at return contents but does not specify the structure (e.g., array of objects). For a 3-parameter tool with full schema coverage, this is minimally adequate but lacks detail on pagination or limits.

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 baseline 3 applies. The description only adds value for url_filter ('optionally filter by URL pattern'), while session_id and clear receive no additional meaning 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 the tool retrieves network requests/responses captured during a session, specifying the data included (status codes, methods, response sizes). It distinguishes itself from general logging but does not explicitly contrast with sibling tools like get_interaction_log.

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 is provided on when to use this tool versus alternatives such as get_response_body or intercept_network. There are no exclusions or context cues for appropriate usage.

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