type

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions fast/human/slow modes, which hints at behavioral variation, but does not explain what those modes do, how typing affects the page, or what permissions/requirements exist.

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 short parenthetical phrase, so it is concise and front-loaded. However, its extreme brevity leaves it under-specified and fragmentary rather than efficiently informative.

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 an 11-parameter input tool with no annotations and no output schema, the description is far too sparse. It hints at locator options and typing modes but omits core behavior, parameter meanings, and usage context an agent needs to call it correctly.

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 only 27%, so the description must compensate for undocumented parameters. It names selector, label, placeholder, index, and mode, but adds no meaning beyond the schema and omits the required 'text' parameter plus clear, delay, timeout, if_exists, and press_enter.

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 says 'unified input' and lists supported locator strategies, which implies typing into an element, but it never states the specific action clearly. It does not differentiate this tool from sibling tools like 'fill' or 'fill_form'.

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 gives no guidance on when to use this tool versus alternatives such as 'fill' or 'press_key'. It only lists capabilities, leaving context and exclusions entirely to inference.

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