browser_emulate_environment

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

No annotations are provided, so the description carries the full behavioral burden and largely fails. It does not say whether the emulation applies to the current page or tab, whether it persists across navigations, whether it can be reset/cleared, or if it requires permissions — all critical for a state-mutating browser tool.

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?

A single sentence with no wasted words is well front-loaded, but here brevity is under-specification rather than economy — the sentence is too thin for a three-parameter state-setting tool.

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 no annotations, no output schema, three undocumented-ish parameters, and two overlapping siblings, the definition is not complete enough for confident invocation. It should at minimum clarify scope (tab/page), reversibility, and its relationship to browser_set_geolocation/browser_set_timezone.

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 coverage is only 33%: timezone_id has an example format, but latitude and longitude are bare numbers. The description's 'coordinates and/or timezone' hints that the pairs are optional and combinable, but adds no format, range, or pairing rules beyond the schema's weak coverage.

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 gives a specific verb ('emulate') and two named resources (geolocation coordinates, timezone), so an agent knows the tool's domain. It stops short of differentiating from the near-identical siblings browser_set_geolocation and browser_set_timezone, leaving unclear whether 'emulate' combines them or duplicates them.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives. Given two direct sibling tools (browser_set_geolocation, browser_set_timezone) that appear to cover the same ground, the absence of any disambiguation is a real gap.

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