browser_fill_form

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions 'smart field matching' without explaining whether it overwrites existing values, triggers input/change events, requires visible fields, or handles hidden elements. This leaves significant behavioral ambiguity.

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, making it concise and front-loaded. However, its brevity comes at the cost of missing critical details, which slightly reduces the score.

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 one complex parameter (array of objects), no output schema, and no annotations, yet the description provides only a high-level phrase. It fails to explain the return value, side effects, or parameter structure, making it inadequate for reliable invocation.

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?

The input schema has 0% description coverage, so the description must compensate. It does not clarify the meaning of 'fields,' 'value,' or 'selector,' nor how 'smart matching' interacts with them. The phrase 'multiple form fields at once' adds minimal context but fails to explain the array-of-objects structure or optional selector behavior.

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 states 'Fill multiple form fields at once with smart field matching,' which clearly identifies the action (fill), the resource (form fields), and the scope (multiple at once). However, it does not explicitly differentiate from the sibling tool 'smart_fill_form,' so it stops short of full sibling distinction.

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 like smart_fill_form or browser_interact. The description implies a bulk-fill use case but offers no exclusions, prerequisites, or contextual cues.

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