convert_time

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

No annotations are provided, so the description carries the full burden. It explicitly discloses DST-transition handling, date-boundary changes, and a no-hardcoded-offset policy, which are meaningful behavioral guarantees. It does not cover error or return behavior, but the key traits for a conversion tool are covered.

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?

Four focused sentences, front-loaded with the core action and followed by behavioral constraints. There is no filler, redundancy, or unnecessary detail.

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 3-parameter tool with no output schema or annotations, the description covers inputs, timezone standards, DST handling, and multi-target conversion. It leaves return format and error cases unspecified, which are minor for this operation.

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 100%, so the baseline is 3. The description reinforces datetime format and IANA names, but mostly repeats what the schema already states; it adds no genuinely new parameter semantics beyond illustrative examples.

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?

States a specific verb ('Convert') and resource ('a datetime between IANA timezones'), and the emphasis on IANA/DST/multiple targets differentiates it from siblings like format_time and timezone_info. The purpose is unambiguous and actionable.

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?

Provides clear context: instructs to use IANA names, forbids hardcoded UTC offsets, and notes multi-target support. It does not explicitly name alternatives or state when-not-to-use, but the constraints are enough to guide correct usage.

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