browser_set_input

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

Describes the mechanism (native setter + events) and return value (value + snapshot). No annotations exist, so description carries full burden. Does not cover error conditions or permissions, but adequately explains the core behavior for the intended use.

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?

Three sentences, no superfluous information. Front-loads the purpose. Efficient and to the point.

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 complexity of controlled inputs, the description explains why the tool exists and how it works. Output schema covers return values. Could mention error handling or invalid ref, but sufficient for core use case.

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 has 3 parameters with 0% description coverage. Description mentions 'value' implicitly but does not explain 'ref' or 'session_id'. The agent can infer ref from context, but lacks explicit parameter guidance.

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?

Clearly states it sets value on framework-controlled inputs (React/Vue) via native setter and events. Distinguishes from siblings like browser_type and browser_fill by specifying the exact scenario where it is needed.

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?

Explicitly advises when to use: when browser_type/fill leaves field empty due to controlled components. Provides concrete examples (OTP, masked phone inputs). Lacks explicit 'when not to use' but the context is clear.

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