tool_convert_timezone

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

With no annotations the description carries the full behavioral burden. 'DST-aware' is a genuinely useful disclosure, but it omits how naive datetimes are interpreted, what happens with invalid IANA names, and what the conversion returns. Helpful but substantially incomplete for a zero-annotation tool.

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 core capability is front-loaded in one sentence and the Args block is compact, with each example earning its place. The inline Args formatting is slightly clunky but wastes no 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?

For a 3-required-parameter tool with no output schema and no annotations, key gaps remain: the return shape (string vs object, timezone label, offset) and error behavior for bad input are unaddressed. The conversion semantics themselves are covered adequately.

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, and it does: the Args block gives concrete formats for datetime_str ('2026-08-15 14:30' or ISO), names the namespace for both zones, and notes 'UTC' is acceptable. It still doesn't clarify ambiguity handling for offset-bearing inputs, so it stops short of a 5.

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 and resource ('Convert a date/time between IANA timezones') and adds a distinguishing capability ('DST-aware'). An agent can identify this as the timezone-conversion tool with no ambiguity against any sibling.

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?

Usage is only implied: the parameter shapes suggest converting a timestamp from one zone to another, but there is no explicit when-to-use guidance, no statement of when not to use it, and no routing to or from alternatives. Adequate minimum viability, no more.

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