intercept_request

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

Describes actions (log, block, modify, mock, stop) and conditional parameters, but lacks details on side effects like persistence or prerequisites (e.g., network capture enabled).

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?

Concise docstring format with clear front-loaded purpose; each sentence adds value, though slightly repetitive in listing parameters.

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 5 parameters and no schema coverage, description fails to fully document return value, data types for complex objects, and prerequisite conditions.

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?

Adds meaning to parameters beyond the schema (e.g., 'url_pattern: URL glob pattern', 'action: log, block, ...'), but lacks precise formats for modify_headers and mock_response dicts.

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?

Clearly states the verb 'Intercept' and resource 'network requests matching a pattern', distinguishing it from siblings like get_network_request 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?

No explicit guidance on when to use this tool versus siblings like get_network_request or list_network_requests; description focuses only on arguments.

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