browser_type

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

Annotations already carry destructiveHint=true and readOnlyHint=false, signaling a mutating operation. The description adds only the 'editable element' scope and does not disclose behavioral traits such as replacing existing text, triggering input events, or requiring permission through the 'element' parameter.

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 concise, front-loaded sentence with no filler or repetition. It is economical, though the brevity comes at the cost of behavioral detail.

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?

Full schema coverage and annotations provide enough structured information for a basic call, and no output schema exists to explain. Still, for a destructive 5-parameter mutation tool, the description could usefully mention that typing may replace content or trigger key handlers.

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 all five parameters are already documented with their individual purposes. The description itself introduces no additional parameter-level nuance, so it correctly sits at the baseline.

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 names a concrete action ('Type text') and a resource ('editable element'), making the tool's function immediately understandable. It doesn't explicitly differentiate it from siblings like browser_fill_form or browser_press_key, but the verb+target phrasing is clear.

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 phrase 'editable element' implies the tool is intended for text entry into input fields or contenteditable regions rather than general keyboard shortcuts. However, it doesn't provide explicit when-to-use guidance, exclusions, or comparisons with sibling tools.

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