fill_form

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that submission is optional, but does not explain that field refs come from a snapshot, what happens after submit (e.g., navigation or waiting), or whether filling triggers side effects.

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 a single, front-loaded sentence with no filler. Every word contributes to the core operation, which is appropriate for a relatively simple tool.

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 is too thin for a mutation tool with no annotations and no output schema. It omits necessary context such as obtaining refs from a snapshot, whether submission may cause navigation, and how this compares with other form-related tools.

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 adds modest context by saying 'multiple form fields' and 'optionally submit', which maps to the 'fields' and 'submit_ref' parameters. However, the schema already documents 'ref', 'value', and 'submit_ref', and the description does not meaningfully deepen the understanding of either parameter.

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 and resource: filling form fields, with an optional submit action. It is clear, but it does not explicitly differentiate itself from siblings such as 'fill', 'smart_fill', or 'form_introspect', relying on the word 'multiple' to imply scope.

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?

No guidance is given about when to prefer this tool over alternatives like 'fill', 'smart_fill', or 'type_text'. The description only implies use for multiple fields, with no exclusions, prerequisites, or alternative-selection criteria.

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