chrome-devtools-mcp-mux

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

The annotations provide readOnlyHint=false, indicating this is a write/mutation operation. The description adds useful context about when to use this tool versus alternatives, but doesn't provide additional behavioral details like error conditions, performance characteristics, or what happens when keys are pressed. With annotations covering the basic safety profile, the description adds some but not extensive behavioral context.

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 perfectly concise - two sentences that each earn their place. The first sentence states the core purpose, the second provides crucial usage guidance. No wasted words, front-loaded with essential 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?

For a relatively simple tool with good schema coverage (100%) and clear annotations, the description provides excellent usage context and differentiation from siblings. The main gap is the lack of output schema, but the description compensates well by clearly explaining when this tool should be selected over alternatives.

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%, so the schema already fully documents both parameters. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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 specific action ('press a key or key combination') and distinguishes it from sibling tools by explaining it's for situations where other input methods like fill() cannot be used. This provides clear differentiation from tools like 'type_text' or 'fill'.

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 explicitly states when to use this tool ('when other input methods like fill() cannot be used') and provides concrete examples of appropriate use cases ('keyboard shortcuts, navigation keys, or special key combinations'). This gives clear guidance on tool selection versus alternatives.

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