browser_set

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

No annotations are provided, so the description carries the full burden of disclosing side effects. It only says 'Set viewport/device/geo/media' and does not indicate whether changes are session-scoped, persistent, reversible, require a reload, or affect other browser state. The optional 'session' parameter hints at session scoping, but the description does not confirm it.

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 phrase with no filler and every word contributes to identifying the operation. It is concise but slightly under-explanatory; there is no structure for parameter details or usage context.

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 tool with no annotations, no output schema, and vague parameter descriptions, this one-line description is far too incomplete. An agent would not know valid values for 'setting' or 'value', what session scope applies, what success or failure looks like, or how this interacts with other browser tools.

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 the baseline is 3. However, the parameter descriptions are largely tautological ('Setting value', 'Session name', 'Setting to change') and do not specify accepted values or formats; the tool description's list of setting categories is the only meaningful addition.

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 uses the verb 'Set' and lists four concrete setting domains (viewport/device/geo/media), making clear this configures browser emulation settings. It distinguishes itself from sibling tools like browser_navigate, browser_click, and browser_state, though it does not explicitly call out that distinction.

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?

There is no guidance about when to use this tool versus alternatives, no mention of prerequisites like an open session, and no context about whether it should be called before navigation or after. Usage is only implied by the word 'Set' and the listed setting categories.

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