scraping_browser_fill_form

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the agent knows this mutates a live page. The description adds the snapshot prerequisite, which is useful context, but says nothing about side effects beyond the fields — whether the form is submitted, whether events fire, or what happens if one ref in the batch is stale. With annotations carrying the safety profile, a 3 is appropriate.

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 action and followed immediately by the prerequisite. No filler or restatement of the tool name.

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 single-parameter, fully schema-documented tool with no output schema, the description covers what an agent needs to invoke it: the batching behavior and where refs come from. It is slightly short on post-conditions — whether filling triggers submission or navigation — which matters given destructiveHint=true.

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 nested fields array already documents name, type enum, ref and per-type value formatting (checkbox "true"/"false", combobox option text). The description adds only the provenance of ref values (from the snapshot), which is helpful but marginal beyond the schema.

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?

Names a specific verb+resource ('Fill multiple form fields') and the batching scope ('in one operation'), which implicitly separates it from the single-field sibling scraping_browser_type_ref. It does not name that sibling directly, so the differentiation is inferred rather than stated.

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 ('Use scraping_browser_snapshot first to get the correct ref values') and a clear preference rule ('more efficient than filling fields one by one'). No exclusion conditions are stated, such as when a single-field type call would still be needed (e.g. needing to observe intermediate state).

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