browser_fill_form

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this mutates external page state. The description adds a general reliability claim but does not disclose what gets overwritten, whether existing values are replaced, or validation/failure behavior — useful context that would go beyond the annotations.

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?

Two tight sentences with the batch capability front-loaded and no wasted words. It is appropriately sized for a tool whose schema carries most of the detail, though it could be marginally sharper by naming the alternatives it beats.

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?

With a rich nested schema, full annotation coverage, and no output schema, the description covers the essentials an agent needs to call it correctly. The only real gap is that a destructiveHint=true mutation never explains what is replaced, but the core capability is 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?

Schema description coverage is 100%, so both the fields array and the snapshot flag are fully documented, including value format for each widget type. The description's widget enumeration (text, checkbox, radio, dropdown, slider) largely restates the type enum, adding no syntax or ordering detail beyond the schema. Baseline 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?

States a specific verb ("Fill") and resource ("several form fields in one call") and enumerates the supported widget types. It implicitly contrasts with the separate typing/clicking siblings (browser_type, browser_click), though it does not name them. An agent can identify the tool's scope without opening the schema.

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?

"Faster and more reliable than separate typing and clicking" implies a preference over browser_type/browser_click, giving implied usage context. However, there is no explicit when-to-use/when-not (e.g., single-field cases) and no named alternatives, leaving the agent to infer.

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