session_network

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

Though the annotations only indicate readOnlyHint=true, the description adds rich behavioral detail: default returns compact rows with specific fields, filter="media" merges DOM candidates, entries carry via="network" or via="dom", and iframe candidates are marked as kind "iframe" to navigate into. This goes well beyond the annotation and helps the agent predict exactly what will happen.

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 description is long but every clause earns its place: primary purpose, filter semantics, reliability rationale, via distinction, default output shape, and usage ordering. The most important scoping sentence is front-loaded, and the detailed nuances are structured with clear separators.

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?

With no output schema, the description must explain the return format, and it does: compact rows with method/url/status/type/size, plus via-tagged entries for media mode. It also covers prerequisites, navigation strategy, and how to handle iframe candidates. Nothing essential for a successful call is missing.

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 the baseline is 3. The description adds value by explaining the runtime semantics of filter="media", including the distinction between confirmed network requests and DOM candidates, and clarifies the default behavior when the filter is omitted. session_id remains minimally described, but it is a straightforward required identifier.

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 opens with a specific verb and resource: 'Read the session's network request log.' It clearly distinguishes this tool from navigation, scrolling, and clicking siblings by focusing on network request inspection, and adds the concrete use case of extracting real media URLs versus HTML-embedded decoys.

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 gives clear operational context: navigate to the video page first, let it load, then call this tool. It also explains when to use filter="media" versus omitting it. However, it does not explicitly name alternative tools or state when NOT to use this tool in favor of a sibling such as download or fetch.

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