browser_fill_form

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

Annotations already signal that this is a mutating operation (readOnlyHint=false, destructiveHint=true), but the description adds no behavioral context beyond the action itself. It does not mention clearing existing field values, requiring a page snapshot's target references, or what the tool returns after filling.

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 four words and contains no filler or unnecessary repetition. The action and resource are front-loaded, making it easy to scan and understand.

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?

Although the schema is thorough, the overall definition is weak on when to use this tool among many browser interaction siblings and on behavioral expectations there is no output schema and no guidance on side effects. An agent could likely call it with a valid schema, but the description alone does not provide enough surrounding context for confident use.

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 provides 100% coverage with detailed descriptions for target, name, type, value, and element. The description itself adds no parameter-level detail, so the baseline score of 3 applies.

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 a specific verb ('fill') and resource ('multiple form fields'), clearly identifying the action. It is more informative than the title and helps distinguish it from single-interaction siblings like browser_type or browser_click, though it does not explicitly name those alternatives.

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 browser_fill_form versus related tools such as browser_type, browser_select_option, or browser_drop. It does not state that this tool is intended for batch form filling or mention any exclusions or prerequisites, leaving tool selection to inference.

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