browser_fill

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

With no annotations, the description does disclose meaningful traits: it verifies the fill, mode=dom dispatches input/change events without native keyboard events, and there is no automatic retry. However, it never explains what verification actually does, what the default native mode entails, or what happens on failure, leaving significant behavioral questions open.

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?

Very short and front-loaded, with each sentence carrying a distinct behavioral point. It is slightly telegraphic, but no sentence is wasted.

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 a 3-parameter mutation tool with no annotations and no output schema, the description covers some behavioral ground but leaves major gaps: ref semantics, native-mode behavior, verification outcome, and error behavior are all absent.

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 0%, so the description must compensate and largely does not. It explains mode=dom only, never defines the default native mode, and gives no meaning for ref (presumably an element reference) or constraints on value.

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?

States a specific verb and resource ('Replace editable text and verify'), so an agent knows this is a fill/overwrite operation rather than a click or select. It does not explicitly differentiate itself from siblings like browser_fill_many or browser_press_key, so it stops short of 5.

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?

Usage is only implied: filling a form field. The one explicit guidance ('prefer manual password entry') is useful, but there is no stated condition for choosing this over browser_fill_many or browser_press_key, and no prerequisites mentioned.

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