chrome-devtools-mcp-mux

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

Annotations indicate readOnlyHint=false, suggesting a mutation, which aligns with 'handle' implying interaction. The description adds context that it's for browser dialogs, but doesn't disclose behavioral traits beyond annotations, such as side effects (e.g., dialog closure, page state changes), error handling, or dependencies. No contradiction with annotations, but minimal added value.

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, front-loaded sentence that directly states the tool's use case. It's appropriately sized with zero waste, but could be more informative. Structure is clear, though brevity limits depth.

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 no output schema and annotations only covering readOnlyHint, the description is incomplete. It lacks details on return values, error conditions, or what 'handle' entails beyond the action parameter. For a mutation tool with browser interaction complexity, more context is needed to guide the agent effectively.

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 descriptions for both parameters: 'action' (accept/dismiss) and 'promptText' (optional text input). The description adds no meaning beyond the schema, as it doesn't explain parameter usage (e.g., when to use promptText for prompt dialogs). Baseline is 3 due to high schema coverage, but no compensation for gaps.

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 states the tool's purpose as handling browser dialogs, which is clear but vague. It specifies 'if a browser dialog was opened' as the condition, but doesn't detail what 'handle' entails beyond the action parameter. It distinguishes from siblings by focusing on dialogs, but lacks specificity about what types of dialogs (e.g., alert, confirm, prompt) or what 'handling' means operationally.

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 minimal guidance: 'if a browser dialog was opened, use this command to handle it.' It implies usage context (when a dialog is present) but offers no explicit when-not scenarios, alternatives, or prerequisites. No comparison to sibling tools like 'click' or 'press_key' for similar interactions, leaving the agent to infer usage.

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