scraping_browser_fill_form

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

No annotations are provided, so the description carries the full burden. It usefully discloses the snapshot dependency and the batching behavior, but says nothing about whether the form is submitted, how stale or invalid refs are handled, or what happens to pre-existing field values.

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?

Three short sentences, front-loaded with the core action and followed by the prerequisite and the efficiency rationale. No filler or redundancy.

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 form-fill tool with no output schema and no annotations, the description covers the action, the dependency, and value handling via the schema. It omits return/error behavior, but as a write-action whose outcome is later observable via snapshot, that gap is minor.

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 100%, and the schema itself documents the value formats for checkbox ('true'/'false') and combobox (option text). The description adds no meaning beyond what the schema already provides, so the baseline 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?

States a specific verb and resource ('Fill multiple form fields in one operation') and contrasts with the one-by-one alternative, which implicitly distinguishes it from the single-field sibling scraping_browser_type_ref. It never names that sibling directly, so it stops short of full differentiation.

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?

Gives an explicit prerequisite sequence ('Use scraping_browser_snapshot first to get the correct ref values') and a rationale for preferring this tool over filling fields individually. It does not state when NOT to use it or how it compares to scraping_browser_type_ref by name, so it remains slightly incomplete.

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