page_network_body

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

With no annotations, the description carries the full burden, but it only presents the body as 'the 0s and 1s layer' and doesn't disclose operational behavior such as base64 encoding, availability only for captured responses, or error cases when the body wasn't saved. It adds a bit of context about engine-side data but no actionable behavioral detail.

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 first sentence is direct and front-loaded, but the remaining sentences — 'THIS is the 0s and 1s layer' — are stylistic filler that adds little semantic value. Not bloated, but not every sentence earns its place.

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 network-body tool with no output schema and no annotations, the definition omits the capture prerequisite, where requestId comes from (except a schema hint), and what the response contains or how it is encoded. An agent would need cross-tool inference to call 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 coverage is only 33%: only request_id has a description. The prose mentions requestId and 'captured response', but it doesn't explain session_id or page_id or the expected format/type of any parameter, so the description does not compensate for the low schema coverage.

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 opening sentence names a specific action ('Fetch the BODY'), a specific resource ('a captured response'), and the selection key ('requestId'), and even names the underlying protocol call. It does not explicitly distinguish itself from sibling tools like page_network_read, but the 'BODY... page JS can't see' phrasing implies the raw-response-body niche.

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?

The description implies when to use it — when you need the raw JSONP/API response data that page JS conceals — but never states a prerequisite (network capture started, requestId obtained from page_network_read) or contrasts it with alternatives. The only cross-reference to page_network_read lives in the schema's request_id description, not in the tool description.

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