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

The annotations carry no positive hints (readOnlyHint is false), so the description carries the behavioral burden and it delivers: it explains that the input is wall-clock in from_zone unless it has an offset or trailing Z, that natural-language times work, and that output includes day-change markers and UTC instant. It does not detail gap/fold resolution, though the schema's parameter descriptions cover those cases.

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 short and front-loaded, with the core action in the first sentence and useful parsing detail in the second. The final example '3pm tomorrow works' slightly duplicates the schema's time examples, so it is not maximally tight, but it is not padding either.

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 no-output-schema tool with natural-language input and DST edge cases, the description gives the essential input semantics and a high-level return shape. It leaves exact output formatting implicit and relies on the schema for gap/fold behavior, which is an acceptable but not exhaustive treatment.

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 the baseline is 3; the description adds value beyond the schema by clarifying the parsing rule for time ('wall-clock ... unless ... offset or trailing Z') and by specifying that all to_zones are included in the conversion. It adds no new detail for gap/fold, but those already have thorough enum descriptions in 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 opens with the specific verb 'Convert' and a precise resource ('one time from from_zone into every zone in to_zones'), making the operation unambiguous. It also distinguishes this from date-time siblings like now, dst_changes, and overlap by stating exactly what it produces: zone conversions with day-change markers and the UTC instant.

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?

It provides clear context for when the tool applies: converting a point in time across zones. It does not name alternatives or explicitly state when not to use it, but the conversion-specific wording is enough to route an agent away from the sibling scheduling and business-day tools.

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