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

No annotations are provided, so the description must carry behavioral disclosure. It only states the core action and does not mention that most of the 9 schema properties are ignored or that only 'zone' is used. The schema itself documents the discarded parameters, but the description does not surface this behavioral quirk for an agent relying on it alone.

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, tight sentence with no wasted words. It is efficiently front-loaded and avoids redundancy or fluff.

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 being a logically simple tool, the presence of 8 apparently irrelevant parameters creates ambiguity. The description does not warn that those parameters are ignored, nor does it name the specific 'zone' parameter to use. Without that context, an agent could easily pass the wrong parameter or be confused by the schema noise.

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% for all 9 parameters, so the schema already documents each property. The description adds slight value by identifying the relevant parameter as an IANA timezone, but it does not elaborate on the other parameters or clarify their lack of effect.

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 and resource: 'Current time in a named IANA timezone.' This clearly differentiates it from sibling tools like iana-zones (list zones) and utc-time (UTC time). An agent can identify its purpose without inspecting the schema.

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?

No guidance on when to use this tool versus alternatives. It does not mention 'use for local time, use utc-time for UTC' or clarify that the zone parameter is the intended one. The usage context is entirely implicit.

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