websex_browser_network_rules

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

No annotations are provided, so the description carries the full behavioral burden. It doesn't disclose whether rules are additive or replace existing ones, persistence across sessions, permission requirements, or any side effects. For a configuration tool that alters browser network behavior, this is a significant gap.

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?

A single efficient sentence that front-loads the core purpose and lists the key configurable elements. It could be expanded slightly for clarity without losing conciseness, but it is well-structured.

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?

The tool has five parameters at 0% schema description coverage and no annotations, and an output schema exists but the description doesn't leverage it. The description fails to explain required parameters, rule format, persistence, or interaction with other browser tools, making it incomplete for correct invocation.

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 description coverage is 0%, so the description must compensate for all five parameters. It only obliquely references three of them (blocked_patterns, url_replacements, extra_headers) in a single phrase, and says nothing about the required engagement_id and session_id or the format for URL patterns and replacements. This is far below the minimum needed.

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 a specific verb and resource: configuring browser request interception. It names three concrete capabilities (blocked URL patterns, URL replacements, extra request headers) that map directly to parameters. It lacks explicit differentiation from siblings like websex_browser_network_log or websex_browser_set_state, but the purpose is unambiguous.

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 on when or why to use this tool versus alternatives. It doesn't say whether this must be called before navigation, whether rules persist across sessions, or how it relates to websex_browser_network_log or websex_browser_set_state. The agent must infer usage entirely.

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