browser_set_form_values

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

With no annotations, the description carries the full behavioral burden yet discloses almost nothing: it does not say whether the fills are atomic (all-or-nothing vs partial), whether the page mutates, submits, or invalidates snapshot refs after filling, or what permissions/session requirements apply. Only the batching hint adds anything beyond the name.

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?

A single front-loaded sentence with no filler. It is efficient, though the second clause partially restates the schema's FormField definition.

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?

An output schema exists, so return values need not be explained, but for a mutation tool with no annotations and 0% parameter coverage the description is far too thin. Key facts an agent needs — atomicity of the batch, post-fill state effects, and the role of observe/session_id/timeout_ms — are all absent.

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%, and the description explains only the fields array ('each item has ref and value'), which the schema already conveys. It says nothing about the observe enum, session_id, or timeout_ms parameters, leaving three of four parameters undocumented in both places.

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 ('Fill') and resource ('snapshot refs'/form values) plus the batch semantics ('several ... in one call'). It doesn't explicitly distinguish itself from the sibling browser_set_value_ref, so the singular-vs-batch scope must be inferred.

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 phrase 'several ... in one call' weakly implies a batch use case versus browser_set_value_ref, but there is no explicit when-to-use, when-not, or alternative routing. An agent is left to guess whether to call this once or the singular tool repeatedly.

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