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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the names are a curated 'common' subset for clock calls, which is a mild behavioral trait. However, it does not explain that the schema parameters appear to be discarded/shape-checked or how the tool handles unexpected inputs.

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 padding, so it is concise in word count. But for a tool with seven confusing parameters and no output schema, this level of brevity is under-specification rather than effective conciseness. The description does not earn its length because it omits essential clarifying 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?

There is no output schema, and the description does not state return format, filtering behavior, or how the parameters relate to the tool's purpose. The agent cannot determine what a call to iana-zones actually produces or why the schema includes refs, URLs, cities, feeds, hosts, JSON, and paths. This is incomplete for a tool with this much schema ambiguity.

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 only ~29%, and the description contributes nothing about parameters. The seven listed properties (ref, url, city, feed, host, json, path) seem unrelated to 'IANA timezone names,' and their individual descriptions suggest discard/shape-check behavior. The description fails to resolve this confusion or compensate for the low coverage.

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 tells the agent the tool is about 'Common IANA timezone names for clock calls,' which identifies the resource and use case. However, it lacks a verb like 'list,' 'get,' or 'validate,' and 'IANA timezone names' largely restates the tool name 'iana-zones.' It is more than a tautology but still vague about the exact operation.

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' implies a context, but there is no guidance on when to use this tool versus sibling tools like 'timezone' or 'utc-time.' No exclusions or alternative-selection criteria are provided, so the agent is left to guess which tool fits a given request.

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