save_response_body

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

With no annotations provided, the description carries the full burden and delivers: never overwrites existing files, rejects truncated bodies by default, never triggers a new request, and clarifies that bytes are Playwright's decoded body (not wire/compression bytes). Return format (path, byte length, SHA-256, partial flag) is also disclosed.

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?

Tightly organized into summary, Args, and Returns sections. The key differentiator ('without refetch/replay') is front-loaded, and every sentence carries information with zero fluff.

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?

Despite no output schema and no annotations, the description covers behavior, all parameters, return values, and edge cases (missing/truncated body, overwrite policy, decoded vs wire bytes). Nothing essential is missing for an agent to invoke it correctly.

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%, so the description fully compensates: request_id (requires a completed body with capture_body=True), save_path (new path, no overwrite), and allow_partial (default rejects truncated bodies) are all semantically enriched beyond the bare schema types.

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?

States a specific verb (save), a precise resource (captured response bytes), and content types (JS/WASM/JSON/binary). The qualifier 'without refetch/replay' clearly differentiates it from sibling network tools like get_network_request, export_network_capture, and list_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?

Provides clear preconditions (capture_body=True required) and failure-path guidance ('increase the capture limit and collect a new sample intentionally'). However, it never explicitly names alternative sibling tools, leaving the when-to-use contrast implicit rather than stated.

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