browser_mouse_down

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not explain that this tool presses and holds the button until a corresponding mouse_up, nor does it mention any side effects or prerequisites (e.g., need for an active page). This is a notable 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?

The description is extremely short and to the point, containing no filler. It communicates the core action in a single phrase. However, it may be overly sparse, omitting useful context that could fit without bloating.

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 large set of sibling browser tools and the absence of annotations or output schema, this minimal description is insufficient. It does not explain the tool's relationship to other mouse actions, when a down event is required, or any state changes (like holding the button).

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 adds no information about the button or clickCount parameters. While the parameter names are somewhat self-explanatory, the description does not clarify allowed values, default behavior, or how clickCount affects the event.

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 indicates the action of pressing a mouse button, which is a specific verb+resource. However, it does not explicitly distinguish this from sibling tools like browser_mouse_click or browser_mouse_up, so it lacks some sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives such as browser_click or browser_mouse_up. There is no mention of scenarios where a down press is needed (e.g., drag-and-drop or holding a button).

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