set_timezone

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It only says 'Set,' which implies mutation, but it does not mention persistence, whether auto timezone is overridden, required permissions, or potential side effects.

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 compact and front-loaded with the purpose, followed by a single clearly formatted Args block. Every sentence adds useful information with no wasted words.

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 simple one-parameter setter, the description provides enough to invoke the tool correctly: purpose, parameter semantics, an example, and a validation source. An output schema exists, so return-value documentation is not required. The main gap is behavioral side-effect disclosure, but the tool is simple enough that the definition is nearly complete.

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 schema provides only a bare string property with no description, but the description compensates fully by explaining the timezone name format, giving a concrete example ('America/Denver'), and directing the agent to list_timezones for valid values.

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 states a specific verb and resource: 'Set the WLAN Pi system timezone.' This clearly identifies the operation and distinguishes it from sibling getters like get_timezone and list_timezones, as well as enable_auto_timezone.

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 gives clear context for using the tool: set the system timezone. It also provides an explicit companion-tool reference: 'use list_timezones for valid values.' It does not explicitly contrast with enable_auto_timezone, but the core usage is clear.

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