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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only the 'Same as GET https://...' equivalence, disclosing that this is a stateless HTTP-backed lookup, but says nothing about output shape or error behavior.

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?

Two short sentences, front-loaded with the primary purpose. The second sentence's HTTP-equivalence note is borderline filler but is compact and arguably useful for cross-referencing.

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 3-param, no-required-arg tool with no output schema, the description does not explain what the response contains or how multiple comma-separated zones are returned. Annotations cover safety, but the return-value burden falls on nothing since no output schema exists.

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 at, tz and from_tz with their formats. The description adds no additional meaning about how these parameters interact (e.g. default UTC, comma-separated zone output), 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 ('Convert a time between IANA time zones') and covers the second mode ('give the current time anywhere'). It does not name or distinguish itself from close siblings like utcNow or dateMath, so it stops short of a 5.

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 implied by the two described modes (conversion with a source zone, or current time with no arguments), which is enough for an agent to infer when it applies. There is no explicit when-not-to-use or routing to the sibling utcNow/dateMath tools that overlap with it.

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