convert_timezone

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

No annotations are present, so the description carries full burden. It discloses input formats and output fields but does not mention error handling, ambiguous time handling (e.g., DST overlaps), invalid timezone behavior, or any rate limits/permissions. Partial but missing important behavioral details.

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 sentences with no wasted words. First sentence states purpose and input capacity; second sentence describes output. Efficient and front-loaded for quick comprehension.

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?

The description covers input formats and output fields but omits error conditions, time range support, and handling edge cases like ambiguous times. Without an output schema, more detail on return structure would be beneficial. Adequate but not fully comprehensive.

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 schema descriptions already cover parameter meanings. The description adds context (example input formats, return fields) but does not significantly enhance understanding beyond the schema. Baseline 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 converts a date/time between IANA timezones, specifies acceptable input formats (ISO 8601 or natural language), and lists return fields (converted datetime, offset, abbreviation, DST flag). It is distinct from sibling tools like convert_batch, date_math, etc.

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 implies the tool is for single timezone conversions but does not explicitly state when to use it vs. alternatives (e.g., convert_batch for batch, now_in for current time, tz_offset for just offset). No when-not or alternative guidance is provided.

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