browser_mock_response

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it reveals nothing about how mocking works, whether it mutates state, persists, or affects other browser operations. There is zero behavioral context beyond the tool's name.

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 short, but this is under-specification rather than conciseness. Every word is wasted because it merely echoes the tool name without providing useful structure or content. There is no front-loading of key information.

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?

Given the tool has two required parameters (one an object) and no output schema, the description provides no guidance on return values, side effects, or expected usage. The description is entirely inadequate for an agent to safely or effectively invoke this tool.

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 mention urlPattern or response parameters. The fallback to schema is empty, so the agent cannot infer what values to provide or how they behave. The description adds no semantic value.

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 '模拟响应' is a direct translation of the tool name ('mock response'), providing no additional meaning. It does not state what the tool does, what resource it acts on, or how it differs from 83 browser sibling tools. This is a tautology.

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 offers no guidance on when to use this tool versus alternatives, no context for its typical use case, and no exclusions or prerequisites. An agent has no basis for selecting this tool over siblings like browser_intercept_requests or browser_wait_for_response.

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