network_recorder

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

With zero annotations, the description carries the full disclosure burden, but it only adds two behavioral hints: the 3x-5x speed-boost claim for block_urls and the intercept/mock behavior of mock_route. It says nothing about side effects of start/stop/clear/clear_routes, whether recorded data persists, whether blocking or mocking survives navigation, or what the get actions return.

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 main purpose is front-loaded in the first clause, and the action enumeration is dense but information-bearing — the parentheticals on block_urls and mock_route earn their place. It is a long single sentence, which slightly hurts scannability, but there is no wasted wording.

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?

This is a high-complexity tool: 14 actions, 6 parameters including nested objects, no output schema, and no annotations. The description answers 'what actions exist' but not 'when to use them', 'what happens when invoked', or 'what the recorded data looks like'. For an umbrella tool of this size, the description is a catalog, not a usable guide.

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 67% (4 of 6 params documented), with the nested filter object and the action enum lacking schema descriptions. The description partly compensates by spelling out all 14 action values with parenthetical meaning for the two least obvious ones (block_urls and mock_route). However, filter's subfields (type, mediaOnly, urlPattern, resourceType) remain unexplained in both schema and description.

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 clear verb+resource statement ('Record, inspect, and control network activity') and then enumerates 14 concrete actions, giving an agent a precise map of the tool's scope. It differentiates from browser-interaction siblings like click/type/navigate through the network focus, though it does blur slightly against api_analyzer and media_extractor given the overlapping get_api_calls/get_media actions.

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 given on when to pick this tool over network-adjacent siblings. The description never names api_analyzer, media_extractor, or redirect_tracer as alternatives, nor does it explain which of the 14 actions fits which scenario. An agent must infer usage entirely from action names.

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