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

There are no annotations, so the description carries the full burden of behavioral disclosure. The phrase 'for clock calls' weakly implies a read-only data resource, but the description does not state that it returns a list, what the output looks like, or whether the listed input parameters are ignored or discarded.

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 short sentence with no wasteful words and the core subject is front-loaded. The lack of detail is a completeness problem rather than a conciseness or structure problem.

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?

With no output schema, no annotations, and a seven-parameter input schema that appears unrelated to the stated purpose, the description is far too thin to let an agent invoke the tool correctly. It does not describe return values, side effects, or how any parameter influences the result.

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?

All seven parameters have their own schema descriptions, so schema coverage is effectively 100% and the baseline is 3. The tool description adds no additional parameter meaning, and it fails to explain how ref, url, city, feed, host, json, or path relate to IANA timezone names.

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 identifies the resource (common IANA timezone names) and the intended domain (clock calls), but it uses a noun phrase rather than an explicit verb such as 'returns' or 'lists'. It also partially restates the tool name (iana-zones → IANA zones) and does not clearly distinguish it from sibling clock-related tools.

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?

'For clock calls' signals the context in which the tool is meant to be used, which is useful guidance. However, it does not explicitly say when not to use it or mention alternatives such as timezone or utc-time, leaving the routing partially implied.

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