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

With no annotations, the description carries the full burden and does so well: it discloses the tz database source, the exact return contents (both sides with offset, abbreviation, DST flag, UTC instant, hour difference), edge-case warnings for nonexistent or ambiguous local times, and the cost/payment mechanism ($0.005 per call via x402 USDC). Those are exactly the traits an agent could not infer from structured fields.

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 trigger condition is front-loaded and every sentence contributes (conversion scope, return shape, DST edge cases, price). It is dense and slightly run-on with stacked colons, but no sentence is filler.

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?

There is no output schema, and the description compensates fully by describing the returned fields and the warning behavior. Combined with complete parameter docs, an agent has everything needed to call it and interpret the result.

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 all three parameters are already documented including the flexible time format. The description adds only the notion that both endpoints are IANA zones, which the schema already states, 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?

States a specific verb and resource: converts between any two IANA zones with DST applied. It clearly frames the task as a conversion rather than a lookup, implicitly distinguishing it from time_now/time_zones, but it never names those siblings to make the split explicit.

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?

Opens with a concrete usage trigger: use when about to commit to a time in someone else's zone and cannot be an hour wrong. That gives a clear condition for invoking it, though no explicit when-not case or named alternative is offered.

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