playwright__browser_fill_form

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

Annotations already indicate this is a destructive, non-read-only operation, but the description adds no behavioral details beyond that—no mention of side effects, submission, permission prompts, or what happens to existing field values. With destructiveHint=true, the agent would benefit from at least a note on the tool's effect on the page.

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?

One short, front-loaded sentence with no filler. It communicates the verb and object efficiently, though it may be too sparse to fully stand alone.

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 tool is a complex mutation with nested parameter objects, but the schema and annotations cover parameter semantics and safety profile reasonably well. Missing is any guidance on when to use the tool or what the result looks like, which leaves the definition adequate but not fully complete.

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 schema fully documents the 'fields' parameter (target, name, type, value, element) with descriptions, so schema coverage is 100%. The description adds no additional parameter semantics but doesn't need to; the baseline of 3 is appropriate.

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 action ('Fill') and resource ('multiple form fields'), making the tool's core purpose clear. It does not explicitly differentiate from siblings such as playwright__browser_type or playwright__browser_select_option, though the plural 'form fields' hints at batch form-filling rather than single-field typing or option selection.

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 provided about when to choose this tool over its siblings. There is no mention of prerequisites (e.g., needing a page snapshot to obtain field targets) or of contexts where filling multiple fields is preferred to repeated browser_type calls.

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