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

There are no annotations and the description does not disclose any behavior, such as error handling for invalid zone names, whether it reads the system clock, or whether it makes network calls. The tool's operational characteristics are entirely opaque.

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, compact sentence with no fluff or redundancy, achieving maximum conciseness while conveying the core purpose.

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?

The description is far too sparse to be complete given the large, noisy schema and the presence of many sibling tools. It omits the key relationship between the tool and the 'zone' parameter, does not mention what output to expect, and provides no context about alternatives or edge cases.

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?

The schema lists 9 parameters, but the description never mentions which one (zone) is the meaningful input. Several parameters (ref, url, city, feed, host, json, path, query) are described as 'discarded after the shape check' but there is no explanation that they are irrelevant. An agent could easily pass the wrong parameter or be confused by the extraneous fields.

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 states the tool returns the current time in a named IANA timezone, which is a specific action and resource. It distinguishes itself from the sibling utc-time (which gives UTC) and iana-zones (which lists zones) by specifying 'named IANA timezone'.

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 provides no guidance on when to use this tool instead of alternatives like utc-time or geo-hint, nor does it indicate any prerequisites or typical use cases. An agent gets no direction on selecting this tool.

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