emulate_timezone

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely restates the tool's name and provides no information about side effects, scope, persistence, or whether the override affects all contexts. The phrase 'override' implies mutation, but there is no detail on how the browser timezone is changed or how it can be reset.

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 sentence and is appropriately concise without any filler. However, it is so brief that it sacrifices useful behavioral and usage context. Still, for what it includes, it is well structured and front-loaded.

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 tool's simplicity (one parameter, no output schema, clear schema documentation), the description is minimal but not fully complete. It lacks usage guidance, behavioral transparency, and any context about when to apply timezone emulation. The schema covers parameters, but the description does not help the agent understand the tool's role relative to siblings or its side effects.

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?

The input schema has 100% coverage for the single parameter timezoneId, including an example list of IANA timezone IDs. The description adds no additional semantic meaning beyond what the schema already provides, so the baseline score of 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?

The description 'Override the browser's timezone' uses a clear verb (override) and specific resource (browser's timezone), distinguishing it from sibling tools like emulate_geolocation or emulate_locale. It does not explicitly call out the distinction, but the resource is specific enough to avoid confusion.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not state that it is for testing timezone-dependent behavior, nor does it mention any prerequisites or exclusions. Sibling tools like emulate_locale and emulate_geolocation exist, but the description does not clarify when timezone is the appropriate choice.

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