Current time in zones

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

With no annotations, the description carries the burden alone and does a good job: it discloses that zones are resolved, that all results share one UTC instant, and what local fields are returned. It could note what happens for invalid/unrecognized places, but for a simple read-only current-time tool this is solid.

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 front-load the core behavior and output shape, then add input flexibility. No filler.

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 read-only tool with one optional parameter and no output schema, the description covers the return contents and accepted input forms. It does not state what happens when zones is omitted or when an input is unrecognized, which is a minor gap.

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 covers the single parameter with a clear example, and the description adds value by listing accepted input forms (IANA zones, cities, countries, abbreviations) and explaining that multiple places can be queried at once.

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 what the tool does: returns the current time for one or more places, with each place's resolved zone, local date, time, offset, and a shared UTC instant. This is specific and distinguishes it from conversion or DST tools.

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 makes the use case obvious ('current time in one or more places') and clarifies accepted input types (IANA zones, cities, countries, abbreviations), but it does not explicitly contrast it with siblings like convert_time or dst_changes, so an agent must infer when to pick this tool.

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