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

The description adds significant behavioral context beyond the annotations: explicit handling of DST gaps and repeated hours, provision of nearby transition evidence, and use of a pinned local time-zone database. Annotations (readOnlyHint, idempotentHint) are consistent, and no contradictions exist.

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 a single sentence that densely packs key features. It is front-loaded with the core action 'Convert... between IANA time zones'. While effective, it could be slightly more readable if split into two sentences, but remains concise.

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?

Given the tool's complexity (5 params, output schema present), the description covers core functionality, special DST handling, and database source. With an output schema, return values need not be explained. A small gap: no mention of required input format constraints beyond schema examples, but overall sufficient.

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 baseline is 3. The tool description does not add extra parameter-level semantics beyond what the schema already provides (clear descriptions for all 5 parameters).

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 clearly identifies the tool's function: converting timestamps between IANA time zones, with specific details about handling DST gaps and repeated hours. It distinguishes itself from generic conversion tools like data.convert, and is unique among siblings.

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?

The description implies usage for timezone conversion but does not explicitly state when to use this tool versus alternatives (e.g., data.convert). No exclusions or when-not-to-use guidance is provided.

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