playwright__browser_fill_form

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

Annotations already provide destructiveHint=true and readOnlyHint=false, so the agent knows this is a write operation. The description adds no further behavioral details (e.g., that it modifies the page, requires user interactions, or handles errors). With annotations present, the bar is lower, but the description still adds no value beyond them.

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 sentence with no wasted words. It is front-loaded and efficient. However, it could be slightly more informative without sacrificing brevity, earning a 4 rather than 5.

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?

Given the tool's complexity (nested array with 5 sub-properties, no output schema), the description is far too minimal. It does not mention that the tool requires target references from a page snapshot, how it handles multiple fields, or what happens on failure. The schema provides structure but the description fails to contextualize the tool's purpose and usage.

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 input schema already documents all parameters clearly (e.g., target, name, type, value). The description does not add any additional meaning or examples beyond what the schema provides. 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 'Fill multiple form fields' clearly states the action (fill) and resource (form fields). It distinguishes from sibling tools like 'type' (single field) and 'click' by implying batch operation, though it could be more explicit about the 'multiple' aspect.

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?

There is no guidance on when to use this tool versus alternatives (e.g., 'type' for single fields, 'click' for interactive elements). No prerequisites, such as needing a page snapshot or target references, are mentioned. The description is too terse to provide usage context.

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