Click

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to state that clicking is a destructive mutation (changes page state), whether it waits for navigation, or what happens if the element is not found. The 9 parameters with complex browser/page management behavior are not explained.

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 a single, concise sentence, but it combines both targeting options without clear separation. It could be improved by front-loading the primary action and then listing alternatives more explicitly. It earns its place but lacks structure.

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 9 parameters, no annotations, and no output schema, the description should provide more behavioral context about page interaction, waiting behavior, and click effects. The existing description only covers targeting, leaving significant gaps for a tool that can change page state.

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 89%, so the baseline is 3. The description adds no parameter-level details beyond what the schema provides, but does not need to significantly compensate given the high coverage. The description's mention of 'CSS selector' and 'snapshotRef' maps to the selector and snapshotRef parameters already documented in the schema.

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 the tool clicks an element, specifying two targeting methods: CSS selector or snapshotRef from dev_browser_snapshot. It provides an example ('e12'), but doesn't fully distinguish this tool from siblings like dev_browser_fill or dev_browser_type, which also interact with elements.

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 does not provide any guidance on when to use this tool versus alternatives. With 16 sibling tools including fill, type, and evaluate, the agent has no context for choosing click over other interactive actions. No when-not-to-use or prerequisite information is provided.

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