datetime_convert_timezone

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'convert,' implying a pure transformation, but does not disclose potential failure modes (e.g., invalid timezone strings), side effects (none expected), or output encoding. The tool likely returns a new string, but this is not confirmed.

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 with a clear category tag and purpose. It is concise and front-loaded. However, it could be more structured, perhaps listing the parameters or expected behaviors in a bullet list. Still, the brevity is acceptable for a straightforward conversion tool.

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?

Given that there is an output schema (though not shown) and three parameters, the description is too minimal to be fully self-contained. It lacks details on accepted datetime formats, timezone identifier standards, and error handling. The agent would need to infer or test these aspects, which could lead to misuse.

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?

The schema has 0% description coverage for parameters, meaning the parameter names and types are the only guidance. The description does not explain what values dt_str, to_tz, and from_tz should take, nor what from_tz defaults to. For example, it does not specify that timezone identifiers should be in IANA format (e.g., 'America/New_York'). The description adds no value beyond the schema.

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 datetime string between timezones, which is a specific verb+resource. It distinguishes from sibling datetime tools like datetime_add_duration or datetime_diff by focusing on timezone conversion. However, it could be more explicit about the expected input format.

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 no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. For example, it does not mention that the input should be in a standard format like ISO 8601, or that from_tz is optional and defaults to UTC. This leaves the agent guessing about appropriate use cases.

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