Browser Fill Form

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that it fills fields and may submit the form, but does not mention potential side effects, error handling, or whether it waits for page updates. It is adequate but not exhaustive.

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?

Two compact sentences with a practical example, front-loaded with the core benefit. No wasted words.

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 description covers the main functionality (fields and submit) but omits details about 'tab' and 'session' parameters, and does not mention error behavior or the output schema (though it exists separately). For a simple form-filling tool, it is mostly complete, but gaps remain.

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 description gives an example for the 'fields' parameter (ref/value) and mentions the 'submit' boolean, adding meaning beyond the schema which only defines an array of objects. However, 'tab' and 'session' are not explained, and schema coverage is 0%, so the description must compensate; it only partially does.

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 exactly what the tool does: 'Fill multiple fields in one call', which is a specific verb and resource, and it contrasts itself with filling one field at a time, distinguishing it from sibling tools like browser_fill.

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?

It implies the primary use case (multiple fields) and notes the optional submit behavior, but does not explicitly name alternatives or provide exclusion criteria. The phrase 'much faster than one fill per field' hints at the alternative but stops short of a direct when-to-use statement.

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