browser_form_fill

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

With no annotations, the description carries full burden and does disclose the fuzzy-matching precedence and which setter is used per element type, plus that results are returned per-key. It omits important behavioral traits: whether input/change/blur events fire, what happens to keys that match nothing, and any permission or page-state prerequisites.

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 core behavior is front-loaded in the first sentence, followed by resolution and setter rules and a compact example. Every sentence contributes; the repeated 'Args:' label is mild overhead but the example it introduces adds value.

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 a nested, free-form-object tool with zero schema coverage and no output schema, the description covers the required `fields` semantics and notes the return shape. However it leaves `tab_id` unexplained and gives no failure/event semantics, so an agent must still guess on tab targeting.

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 0%, so this is where the description earns its keep: it fully explains the free-form `fields` object, including the key-resolution chain (CSS selector → name → label → placeholder) and value handling per element type, with a concrete example. The second parameter, `tab_id`, is never mentioned in either schema or description, leaving one gap.

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?

States a specific verb and resource ('Fill many fields at once') with a clear scope modifier ('many') that implicitly distinguishes it from the single-field browser_fill sibling. It does not name the alternative tool, so differentiation still requires the agent to infer from the sibling list.

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?

Usage is only implied: the batch framing suggests using this instead of browser_fill when filling multiple fields, but there is no explicit when-to-use, when-not-to-use, or named alternative. No guidance on prerequisites such as needing the form loaded or a specific tab.

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