datetime_convert_timezone

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of DST edge cases, how ambiguous or nonexistent local times are resolved, or what the response contains, all of which are real behavioral concerns for timezone conversion.

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?

A single front-loaded sentence with zero padding — the conversion direction is stated immediately. It is arguably under-specified rather than bloated, but structurally it is clean.

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?

With 0% schema coverage and no output schema, the description is the only documentation an agent gets, and it omits both input formats and return shape. For a datetime operation where string format ambiguity causes failure, this is a meaningful 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 description coverage is 0%, so all three parameters are bare untyped-prose strings with no documentation. The description only restates the parameter roles implicitly and gives no format guidance (e.g. '2024-01-01T12:00:00Z' vs '2024-01-01 12:00', 'America/New_York' vs 'EST'), leaving the single most error-prone aspect of the call unspecified.

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 uses a specific verb ('Convert') and resource ('a datetime... timezone') with both source and target scope stated, which is more than the bare name gives. It is distinguishable from siblings like datetime_current_time and timezone_info, though it does not name those alternatives explicitly.

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?

There is no guidance on when to use this versus the several other datetime/timezone siblings, and no stated preconditions. It also omits any hint about accepted input forms (ISO 8601 strings, IANA identifiers vs abbreviations), which is exactly what an agent needs before calling.

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