browser_fill_form

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

No annotations are present, so the description must carry the behavioral disclosure burden. It only restates the fill operation and the per-field requirement, without explaining what happens on partial failure, whether existing values are overwritten, whether it waits for elements, or how frameSelector affects targeting.

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 sentence with no filler and the main behavior is front-loaded. It is terse to the point of underspecification, but every phrase earns its place.

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?

Given no annotations, no output schema, and a nested field object with four properties, this short description leaves the agent unable to predict return behavior, error semantics, or correct field resolution. It should explain how selectors, refs, and names differ and describe batch behavior more thoroughly.

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 compensate. It mentions 'selector or ref' and 'value', but omits the `name` alternative and the `timeout` and `frameSelector` parameters, and it states fields 'need' selector/ref even though the schema only requires `value` per item.

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 leads with a specific verb ('Fill'), a clear resource ('form fields'), and a batch qualifier ('multiple ... at once'), which separates it from sibling tools like browser_fill or browser_type. There is no ambiguity about what operation the tool performs.

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 explicit when/when-not guidance or naming of alternatives such as browser_fill or browser_type. The 'multiple ... at once' phrasing only implies the intended use case, leaving the agent to infer the selection rule rather than being told directly.

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