view-network-request-details

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

Discloses sensitive headers redacted, large response bodies truncated, and error message return if requestId not found. With no annotations, these behavioral details are valuable, though auth or rate limits not mentioned.

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 sentences, no fluff. Front-loaded with main purpose, each sentence serves a clear function.

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?

No output schema, but description sufficiently explains return values and links to sibling tool for valid requestId. Covers key user needs for a details endpoint.

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 description adds value by explaining requestId source (view-network-logs), default of includeBody, and error return context. Slightly beyond 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 it gets full details of a specific network request by requestId, listing returned data (headers, status, timing, optionally body). It distinguishes from view-network-logs which lists 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?

Explicitly says when to use: 'when you need headers, body, or timing for a specific request after listing logs'. Also advises to get valid requestId from view-network-logs and describes error behavior.

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