browser_fill_form

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

No annotations exist, so the description must disclose behavior. It only mentions 'fill', lacking details about validation, event firing, error handling, or constraints (e.g., field types not in enum). The agent is left guessing.

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, efficient sentence without wasted words. However, it lacks structure (e.g., bullet points) and could benefit from additional context while still being concise.

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 (array of objects) and no output schema, the description is incomplete. It does not explain post-fill behavior, supported field types, or how to handle errors, leaving significant gaps for the agent.

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 input schema has 100% description coverage for parameters, providing clear semantics for ref, name, type, value. The description adds no extra meaning beyond 'multiple fields', so baseline score 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 clearly states the action ('Fill multiple form fields') and the resource ('form fields'). It distinguishes from sibling tools like 'browser_type' which fills one field at a time, and 'browser_click' which interacts differently.

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 description implies usage for filling multiple fields simultaneously, but does not explicitly state when to prefer this over alternatives (e.g., browser_type for single fields). No exclusions or context are provided.

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