browser_type

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

With no annotations, the description carries the full behavioral burden, and it discloses only one useful trait: the typed text is not echoed back in the output, so the agent knows not to expect verification from the response. It says nothing about what clearing does to existing content (the `clear` default of true silently wipes fields), whether a submit fires, what triggers a failure, or how `trusted`/`backend` change focus and OS-level input behavior.

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?

Two short sentences, front-loaded with the action, and the second sentence earns its place by flagging a real output caveat. No filler or repetition, though the space saved is spent on a caveat rather than on the default-behavior facts an agent needs.

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?

A 7-parameter mutation tool with no annotations, no output schema, and undocumented defaults for `clear` and `submit` needs substantially more than two sentences. An agent calling this blind risks wiping a field it meant to append to, or triggering an unintended form submission.

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 coverage is 57%: `ref`, `tabId`, `backend`, and `trusted` are documented in the schema, but `text`, `clear`, and `submit` have no descriptions anywhere. The description does not compensate — it never explains that `clear` defaults to true (destroying existing value) or that `submit` may fire a form — which are exactly the semantics an agent must reason about.

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?

"Type text into an element" gives a specific verb (type) plus target (an element), which is clearly distinct from browser_click or browser_navigate. It stops short of differentiating itself from browser_fill_form or browser_press_key, which also send keystrokes, so an agent cannot tell from the description alone which to pick.

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?

There is no when-to-use guidance and no mention of alternatives such as browser_fill_form (multi-field), browser_fill_form/browser_press_key, or the upstream browser_snapshot/browser_find needed to obtain a ref. Nothing is said about prerequisites like the element being visible, focusable, or in the current tab.

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