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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: explicit handling of ambiguous/skipped DST-boundary times, the exact set of returned values, and a per-call price with the x402/USDC payment mechanism. That payment requirement is a real operational prerequisite not in any structured field.

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 core conversion and output inventory, then the DST-edge caveat, then pricing last. Dense but every sentence carries information; the two-direction phrasing is slightly repetitive of the parameter semantics but not wasteful.

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 enumerates the return fields (local date/time, offset in two formats, abbreviation, DST flag, ISO week date, day of year) and warns about DST boundary ambiguity. It is nearly sufficient for correct invocation; only sibling routing against time_dst is missing.

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%, so the schema already documents zone, local, instant and the ambiguous enum, including defaults and mutual exclusivity. The description's mention of ambiguous/skipped local-time handling adds conceptual context but no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

It states a precise bidirectional operation on a specific resource: convert an instant to wall-clock time in an IANA zone, or the reverse. The returned fields are enumerated concretely. It does not differentiate itself from the sibling time_dst, which overlaps on the DST/offset territory.

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?

Usage is only implied through the mutually-exclusive local/instant modes; there is no explicit when-to-use-this-vs-time_dst or when-not guidance. An agent must infer that this tool stays within a single named zone rather than doing multi-zone DST lookups.

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