agent-browser-mcp

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 mentions the optional click behavior but lacks critical details: whether this simulates real keyboard events (vs. programmatic text insertion), what 'real keyboard' means in automation context, whether it respects focus/selection, what happens with special characters, or any rate limits. The description provides minimal behavioral context beyond the basic operation.

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 at 10 words, front-loading the core functionality ('Type text via the real keyboard') followed by the optional enhancement ('optionally after clicking a field'). Every word earns its place with zero redundancy or unnecessary elaboration.

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 this is an automation tool with 4 parameters, 0% schema coverage, no annotations, but with an output schema, the description is insufficiently complete. It doesn't explain the automation context, what 'real keyboard' means technically, coordinate systems for clicking, or typing behavior details. While the output schema may document return values, the description lacks critical context for proper tool selection and invocation.

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%, so the description must compensate for undocumented parameters. The description mentions 'optionally after clicking a field' which hints at the click_x/click_y parameters, but doesn't explain what 'interval' controls (typing speed/delay) or provide context about coordinate systems. With 4 parameters and 0% schema coverage, the description adds only marginal semantic value beyond what parameter names suggest.

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's purpose: 'Type text via the real keyboard, optionally after clicking a field.' This specifies the verb ('type') and resource ('text'), and distinguishes it from keyboard shortcut tools like 'hotkey'. However, it doesn't explicitly differentiate from text-input alternatives like 'execute_js' for web page text entry.

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 implies usage context with 'optionally after clicking a field', suggesting this tool is for text input in UI contexts. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'execute_js' for web page text manipulation or 'cdp_command' for browser automation. No exclusion criteria or prerequisites are mentioned.

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