chrome-devtools-mcp-mux

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

Annotations indicate readOnlyHint=false, implying a mutation, which aligns with 'clicks' as an action that changes UI state. The description adds minimal behavioral context beyond this, not detailing effects like page navigation, event triggers, or error handling. It doesn't contradict annotations, but offers little extra insight for a mutation tool.

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, direct sentence with zero wasted words. It front-loads the core action ('clicks') and is appropriately sized for a simple tool, making it easy to parse quickly.

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 mutation tool with no output schema and minimal annotations, the description is incomplete. It lacks details on return values, error cases, or interaction effects (e.g., what happens after clicking). Given the complexity of UI automation and sibling tools, more context is needed for effective use.

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 100%, with clear docs for 'uid', 'dblClick', and 'includeSnapshot'. The description adds no parameter-specific semantics beyond implying 'uid' identifies an element, which is already covered in the schema. This meets the baseline for high schema coverage.

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 action ('clicks') and the target ('the provided element'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'press_key' or 'hover' that also involve UI interactions, though the verb 'clicks' is distinct enough to imply a mouse click action.

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. It doesn't mention prerequisites (e.g., needing a page or element from a snapshot), exclusions, or comparisons to siblings like 'press_key' for keyboard actions or 'hover' for mouse hovering, leaving the agent to infer usage context.

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