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

With no annotations, the description bears full responsibility for disclosing behavior. It only states the output ('current time') and does not mention return format, error handling for invalid zones, whether a network or system clock is consulted, or that all non-zone parameters are ignored. This is a minimal disclosure that leaves important behavioral traits unstated.

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 eight-word sentence with no filler or redundancies. It is appropriately sized for a tool of this simplicity and front-loads the essential information.

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?

Given the nine optional parameters and the absence of an output schema, the description is incomplete. It does not tell the agent that only 'zone' is relevant, nor does it describe what the returned time looks like. The agent must reason from the schema to determine the correct call, which is unnecessarily ambiguous.

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 input schema already provides 100% coverage, describing 'zone' as 'IANA timezone name' and other parameters as discarded. The tool description merely restates the zone concept without adding guidance about which of the nine optional parameters to use. It adds no semantic value beyond the schema.

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 tool's function: return the current time for a given IANA timezone. This distinguishes it from siblings like utc-time (presumably UTC-only) and iana-zones (listing zones). It is not a tautology and conveys the core operation, though it lacks a verb like 'get' or 'return'.

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 phrase 'named IANA timezone' implies when to use the tool, but there is no explicit guidance on when not to use it or how it compares to alternatives such as utc-time. The agent must infer the use case from the description alone, with no exclusions or alternative routing.

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