Convert a time between zones

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add genuine value: the wall-clock interpretation rule, the offset/trailing-Z exception, and the natural-language input support. However, it omits the output format and error/edge-case behavior (though the gap/fold enums are already documented in the schema), so coverage is partial rather than comprehensive.

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?

Three sentences with zero waste. The primary action is front-loaded in the first sentence, the interpretation rule follows, and the accepted formats close it out. Every sentence earns its place with distinct information.

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?

Input handling is well covered (parsing rules, accepted formats, zone interpretation), and the gap/fold DST edge cases are documented in the schema. But with no output schema and no annotations, the description should have disclosed what the response looks like or how results are shaped; its omission leaves an agent to invoke the tool without knowing what to expect back. Moderate complexity (4 optional edge-case params) was not fully exploited.

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%, so baseline is 3, but the description adds real meaning beyond the schema: it explains that 'time' is read as wall-clock in from_zone unless it carries an offset or trailing Z, enumerates accepted formats (datetime string, ISO, '3pm tomorrow'), and clarifies that multiple target zones are expected. This materially helps an agent construct valid inputs.

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 states a specific verb ('Convert'), resource (time), and scope ('from one place to others'), making the core function clear. The parsing rules and accepted input formats add further specificity. However, it does not differentiate itself from sibling tools like 'convert' or 'convert_many', which could plausibly do the same job.

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?

No guidance is given on when to use this tool versus the several time-related siblings ('now', 'convert', 'convert_many', 'dst_changes', 'business_days'). There is no mention of exclusions, prerequisites, or conditions that would select this tool over an alternative.

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