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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It is a single line that reveals nothing about side effects, that non-zone parameters are discarded, or the nature of the operation, leaving the agent to assume it is a safe read.

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?

A single, waste-free sentence that is fully front-loaded. It is appropriately brief, though the brevity edges toward under-specification given the tool's 9-parameter surface.

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 9 optional parameters, no annotations, and no output schema, the description says almost nothing about how to invoke the tool correctly — it does not indicate that 'zone' is the operative parameter or that the rest are ignored. The rich schema compensates partially, but the description alone is thin for this complexity.

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 schema richly documents each of the 9 parameters, including which are discarded, and the description adds no parameter detail beyond the schema's own notes.

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 states a specific verb-resource pair ('Current time in a named IANA timezone'), clearly identifying the tool as a time lookup. It is implicitly distinct from sibling 'utc-time' (which is UTC-specific), though it does not explicitly name the distinction.

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 offers no guidance on when to use this tool versus alternatives like 'utc-time' or 'iana-zones'. With siblings covering UTC and zone listing, an agent gets no help choosing among them beyond inferring from the name.

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