convert_time

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

With no annotations, the description discloses important behavioral traits: the omission of the source timezone when it would duplicate the input, and the inclusion of configured default timezones. These go beyond a simple 'convert' and provide useful behavioral context for an agent.

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 a single sentence that front-loads the core action and packs in key behavioral nuances. Every phrase earns its place, with no redundancy or fluff.

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?

Although an output schema exists, the description does not explain the 'fold' parameter, which is crucial for ambiguous times around DST transitions. It also does not clarify default behavior when source_timezone is null. The description covers main purpose but is incomplete for a nuanced conversion tool.

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 description coverage is 0%, so the description must compensate. It indirectly explains 'time' (timestamp), 'source_timezone', and 'output_timezones' via 'requested additional timezones'. However, the 'fold' parameter is entirely unexplained, and timezone/time format details are omitted. The description adds some meaning but leaves gaps.

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 'timestamp from a source timezone', making the primary purpose unambiguous. Even without sibling tools, it distinguishes the conversion task and hints at multi-timezone output.

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 provides clear context on behavior: it returns configured default timezones plus any requested additional timezones, and omits the source timezone when duplicated. This tells the agent what to expect, though it does not explicitly state when to use versus alternatives (no siblings exist).

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