safari_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 of behavioral disclosure. 'Fill' implies a write operation, but the description does not say whether existing field values are overwritten, whether events are triggered, whether the page is submitted, or what happens if a selector does not match.

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 or redundancy. Every word contributes to the core meaning, making it highly efficient even though it is brief.

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 an unannotated mutation tool with no output schema, the description is too sparse to fully guide an agent. It lacks usage alternatives, side effects, edge-case behavior, and any context about why this tool exists alongside safari_fill and safari_fill_and_submit.

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%, so the schema already documents fields, selector, value, and receipt. The description adds little beyond the word 'multiple' and 'at once,' which loosely aligns with the array-shaped fields parameter but does not add meaningful semantic detail.

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: 'Fill multiple form fields at once.' This clearly describes the bulk-fill action and distinguishes it from single-field fill tools like safari_fill, though it does not explicitly name sibling alternatives.

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 'multiple form fields at once' implies the tool is meant for batch filling, which provides some usage context. However, it gives no explicit guidance about when to choose this tool over safari_fill, safari_type_text, or safari_fill_and_submit, and it does not mention exclusions.

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