cloak_set_timezone

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

With no annotations, the description carries full behavioral burden. It does disclose a useful trait – the override is live via CDP and requires no relaunch – but omits whether it persists, whether it resets on navigation, and what happens to the previous timezone.

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 tight sentence with no waste, and the key scoping detail ('active context') is front-loaded before the mechanism note.

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 one-parameter setter with no annotations and no output schema, the description conveys scope and mechanism but leaves meaningful gaps: the timezone value format and the override's persistence/lifetime.

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% and the single parameter is a bare string. The description adds no semantics about the accepted timezone format (e.g., IANA identifier like 'America/New_York'), so an agent must guess the expected value.

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?

States a specific verb and resource ('Live-override the timezone for the active context'), making clear it sets the timezone. It implicitly distinguishes itself from the cloak_set_locale/geolocation/proxy siblings by naming the timezone, though it never explicitly differentiates 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?

The phrase '(no relaunch)' implies the usage condition: change the timezone on a running context without restarting. However, there is no explicit when-to-use guidance, no contrast with the other cloak_set_* overrides, and no mention of prerequisites.

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