browser_set_offline

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

No annotations are provided, so the description carries full burden. It states the tool 'toggles the context's network offline/online', indicating a state change. However, it does not disclose the scope (e.g., affects all tabs), whether it is reversible (implied by toggle), or the exact effect on network requests. This is adequate but lacks detail.

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, front-loaded sentence with no wasted words. It conveys purpose and context efficiently.

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 two parameters, no annotations, and an output schema, the description is too minimal. It does not explain return values, side effects on the session, or how the toggle interacts with other network settings. More detail is needed for complete understanding.

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. It does not explain the 'offline' boolean parameter (default true) or the optional 'session_id'. The description adds minimal value beyond the parameter names, failing to clarify their semantics.

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 uses the specific verb 'Toggle' and clearly identifies the resource ('network offline/online') and the purpose ('to test offline behavior'). This distinguishes it from sibling tools like browser_set_proxy or browser_block_urls.

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 explicitly states the use case: 'to test offline behavior'. This provides clear context for when to use the tool, though it does not include when-not-to-use or alternatives, which are not critical for a simple toggle.

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