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

Annotations only cover safety (readOnly, idempotent, closed-world); the description goes well beyond them, disclosing the returned fields, the three-tier confidence vocabulary and that low confidence comes with a reason, that governing statutes are quoted with Federal Register citations, and that output carries an attribution line and permalink. That is exactly the behavioral context annotations cannot convey.

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?

Front-loaded with the capability in the opening sentence and the motivation in the second. The output enumeration in the first sentence is list-heavy, and the attribution/permalink note is a minor tail, but nothing is redundant or padded.

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 no output schema, the description correctly takes on the return-value burden and explains confidence tiers and citations. Minor gaps remain: it does not say how ambiguous or unresolvable place names are handled, nor what the confidence applies to (the zone determination versus the offset), which matters given the tool's whole value proposition is reliability.

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 100%, including the date range 1800-2200 and the midday default for time, so the baseline is 3. The description adds only indirect parameter meaning through the Knoxville example, which hints that 'place' must be granular enough for historic boundaries to matter, but it states no parameter rules itself.

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?

A specific verb ('resolves') plus a precisely scoped resource: the UTC offset in force at a place on a date, plus an enumeration of what comes back (IANA zone, signed offset, UTC instant, confidence, statute citation). No sibling tool does historic timezone resolution, so the boundary is unambiguous without reading any schema.

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?

Strongly establishes when this tool is required over a generic present-day zone lookup, via the explicit Tennessee/Knoxville counter-example ('the present-day zone map can give the wrong offset for a past date'). It stops short of naming sibling alternatives such as convert_calendar_date or stating exclusions (e.g., future dates), so it is clear context rather than full when/when-not routing.

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