browser_type

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

With no annotations, the description must disclose behavioral traits, but it only states the basic action. It does not reveal whether typing is sequential, whether it supports special keys, whether it triggers events, or what the 'submit' and 'slowly' parameters do. This is insufficient for a tool with several behavioral parameters.

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 with no waste. However, it is under-specified, lacking essential context about parameters and behavior, so while concise, it is not optimally informative for the agent.

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?

The tool has 5 parameters, no annotations, and no output schema, yet the description is only seven words. This is grossly inadequate for an agent to understand how to invoke the tool correctly, including required 'ref' and 'text', and optional behaviors like 'slowly' and 'submit'.

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 explain parameters. It only mentions 'text' implicitly, but does not clarify 'ref', 'slowly', 'submit', or 'element'. The description adds almost no value over the parameter names in the schema.

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 identifies the action (Type) and the target resource (an editable element), making it easy to understand what the tool does. It distinguishes itself from siblings like browser_click or browser_navigate, though it could more explicitly differentiate from browser_fill_form or browser_press_key.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or context such as whether the element needs to be focused or visible, nor does it compare with similar browser actions like press_key or fill_form.

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