Resolve a city or country name to its IANA timezone(s) so you don't need the exact identifier — e.g. 'Delhi' -> 'Asia/Kolkata'. Use it first when you only have a place name.
| Name | Required | Description | Default |
|---|---|---|---|
| city_or_country | Yes | City or country name, or ISO country code. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description covers basic input-output behavior and gives an example, but does not address edge cases (e.g., multiple timezones for large countries) or error handling.
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?
Two concise sentences, no wasted words, front-loaded with the primary action and an example.
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 simplicity (1 param, no output schema, no annotations), the description is largely complete. Could note that multiple timezones may be returned for large countries.
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% and description restates the parameter's purpose from the schema, adding only an illustrative example. 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 clearly states the tool resolves a city/country name to IANA timezone(s) with a concrete example, distinguishing it from sibling tools like list_timezones or convert_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?
'Use it first when you only have a place name' provides clear when-to-use guidance. Lacks explicit when-not-to-use, but sibling context implies alternatives.
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.