Convert a single instant into many IANA timezones at once — a world-clock view. Like convert_timezone, but 'to' is a list of target zones.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | List of target IANA timezones. | |
| from | Yes | Source IANA timezone. | |
| datetime | Yes | ISO 8601 or natural language. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It does not disclose error handling, limits on the list size, performance implications, or the return format (especially important without an output schema).
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 purpose and usage, with no extraneous 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?
Given the absence of an output schema, the description should explain the return format, but it does not. It also lacks behavioral details like supported datetime formats or error handling.
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 100%, so baseline is 3. The description adds minimal value beyond what the schema provides; it clarifies that 'to' is a list of zones, but does not elaborate on datetime format or constraints.
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 'convert' and the resource 'a single instant into many IANA timezones', and explicitly distinguishes from sibling 'convert_timezone' by noting the list parameter.
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?
It describes when to use the tool ('world-clock view' vs. single conversion) and names the alternative 'convert_timezone', but does not explicitly exclude cases or list prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: conversion (single and batch), arithmetic, meeting scheduling, holiday checking, timezone lookup, current time, and offset. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., convert_batch, list_timezones, is_holiday). Minor variations like 'now_in' and 'tz_offset' still adhere to the pattern.
Nine tools is ideal for a timezone toolkit. Each tool serves a distinct and necessary function without being excessive or insufficient for the domain's scope.
The toolset covers all major timezone operations: conversion, arithmetic, current time, offset, discovery, holidays, and meeting slot calculation. No obvious gaps for common use cases.