browser_set_offline

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

With no annotations, the description carries the burden of disclosing behavior. It merely states a literal action without explaining effects like whether existing connections are dropped, whether all contexts are affected, or how to revert. The boolean parameter's true/false meaning is not clarified.

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 extremely concise with no fluff, which is positive. However, it is under-specified for an agent to act reliably; a few additional words about the parameter or effect would greatly improve it without adding sizeable length.

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?

For a simple boolean toggle, the description is insufficient. There is no output schema, no annotations, no context about when to use it, and the parameter meaning is ambiguous. The tool could be misused because the agent lacks essential information about the offline flag.

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% and the description does not explain the single 'offline' boolean parameter. The agent cannot infer whether true means offline or online, nor the default behavior. This is a critical gap for a one-parameter tool.

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 means 'Set offline mode', which is a specific action on the browser's network state. It identifies the tool's purpose unambiguously, but doesn't fully distinguish it from other browser settings tools beyond the unique 'offline' concept.

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 usage guidance is provided. The description doesn't mention when to use this tool instead of other browser settings tools, nor does it explain the implications of enabling offline mode (e.g., network requests will fail).

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