browser_set

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool returns a fresh snapshot and explains how values are interpreted per control type. However, it does not mention side effects like waiting, scrolling, triggering events, or behavior on failure, which would make the behavior more transparent for an agent.

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 compact sentence that packs the core operation, per-control value semantics, and return behavior with minimal waste. The arrow-based formatting is slightly dense but remains scannable and front-loads the primary verb and target.

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 two-parameter tool with no annotations and no output schema, the description provides enough to invoke it correctly: what to set, how each control type interprets the value, and what is returned. Minor gaps remain around array values for multi-selects and whether actions wait for the element, but these are not critical for basic use.

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. It clarifies that 'n' refers to an element number and explains 'value' semantics for inputs, selects, and checkboxes/radios. The array form of 'value' is not explicitly addressed, but the core parameter meaning is well covered beyond the bare schema.

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 verb ('Set') and resource ('element #n'), and clarifies the operation by mapping value semantics to control types (inputs, selects, checkboxes/radios). It is clear and actionable, though it does not explicitly distinguish itself from sibling tools like browser_type or browser_form.

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 gives direct guidance on when to use the tool for different control types: inputs should be filled, selects should receive an option value, and checkboxes/radios should receive true/false. It does not mention exclusions or name alternatives, but the control-type mapping provides clear usage context.

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