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 conveys a read-style lookup, but says nothing about output format, what happens on invalid timezone names, dependencies, or side effects. For a tool with no annotations, this is a significant gap.

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 front-loaded sentence with no filler or repetition. Every word contributes to stating the tool's purpose, even though other dimensions suffer from the extreme brevity.

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?

Despite the tool's apparent simplicity, the description omits the crucial mapping between 'named IANA timezone' and the parameters, and no output schema or annotations fill that gap. An agent cannot confidently determine which parameter to pass or what result to expect.

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 description says 'named IANA timezone,' but the input schema contains no timezone parameter at all; the closest candidate, 'city', is described as a weather hint that is discarded. The 7 schema parameters are individually documented, but they are unrelated to the described purpose, and the description does nothing to map the required timezone input onto any parameter.

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 operation: obtaining the current time for a named IANA timezone. This is clear and distinguishes it from siblings like iana-zones (zone list) and utc-time (UTC clock), though it doesn't explicitly name those alternatives.

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 the tool is for current time in a named IANA timezone, but gives no guidance on when to prefer it over utc-time or iana-zones, nor any exclusion or alternative. An agent must infer the intended usage from the tool name and one-line description.

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