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

No annotations are provided, so the description carries the full burden, yet it discloses almost no behavioral context: it doesn't state that the many other input fields are ignored/decoy, how an invalid or missing zone is handled, or what the returned time looks like. 'Current time' implies a read, but not enough for a tool with 9 optional unrelated parameters.

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 front-loaded sentence with no filler; every word earns its place in stating the core function.

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 simple read-only time lookup the minimal description is nearly adequate, and the schema fills in the zone parameter. However, given the unusual schema with nine unrelated optional fields and no output schema or annotations, the definition should clarify which input actually matters and what the caller receives.

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%, including the zone parameter description ('IANA timezone name, e.g. Europe/Paris'), so the schema already carries the parameter meaning. The description reinforces that the relevant input is a named IANA timezone but adds no new format or value constraints.

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 identifies the resource as a named IANA timezone and the desired output as the current time, which distinguishes it from sibling tools like iana-zones (zone listing) and utc-time (UTC). It lacks an explicit verb, but the intent is unambiguous.

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 phrasing implies using this tool when a caller wants the current time in a specific IANA timezone, and the sibling list suggests alternatives, but the description itself gives no explicit when/when-not guidance or named alternatives.

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