set_timezone

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

With no annotations provided, the description carries the full burden. It discloses the side effect of restoring the system timezone when passed an empty string, and implies the tool is a mutation (override). However, it does not detail whether the change is temporary or persistent, what permissions are required, or any potential unintended consequences.

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 extremely concise: two sentences that front-load the main purpose and efficiently cover both normal use and the special case. Every word serves a purpose, and there is no verbosity or redundancy.

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 nested objects), the description covers the core functionality and the important edge case. The presence of an output schema means return values need not be explained. It could be slightly more complete by clarifying the scope of the change (e.g., global vs. per-session), but overall it is adequate.

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 provides no description for the 'timezone_id' parameter (0% coverage). The tool description adds value by giving examples of valid values and explaining the empty string behavior, which partially compensates. However, it does not explain the expected format or list valid options beyond the two examples.

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 clearly states the verb 'override' and the resource 'IANA timezone', provides concrete examples ('Europe/Amsterdam', 'America/New_York'), and explains the special case of passing an empty string to restore the system timezone. This effectively distinguishes it from sibling tools that deal with browser automation and network configuration.

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 description implies usage for setting a custom timezone or restoring the system default, but it does not explicitly state when to use this tool versus alternatives (e.g., set_locale or set_geolocation). There is no mention of prerequisites or contexts where this tool should not be used.

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