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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It completely fails: there is no mention of side effects, output, input handling, or read-only behavior. The schema hints that several parameters are 'discarded', which conflicts with any expectation that inputs matter, but the description does not explain this.

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 short, but brevity is due to under-specification rather than efficient structuring. It is a single fragment that omits a verb and all operational details, so it does not earn its place as a useful tool guide.

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?

Even for a reference-list tool, the description is incomplete. It has no output schema, no annotations, and 9 optional parameters, yet says nothing about return values, when to call it, or how parameters affect 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?

Although schema description coverage is 100%, the parameter descriptions are generic and unrelated to timezone data (e.g., git ref, URL, weather hint) and include 'discarded' notes. The tool description adds no connection between these parameters and IANA zones, leaving an agent uncertain what to pass or why any parameter exists.

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 'Common IANA timezone names for clock calls' is a noun phrase without a verb. It names the resource (IANA zones) but does not state what the tool does with them (list? validate? convert?). The name 'iana-zones' plus description is close to tautological and fails to distinguish from sibling tools like timezone or utc-time.

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 over alternatives. It vaguely mentions 'for clock calls' but does not say what situation calls for it, nor does it mention any sibling tool or exclusions. An agent cannot tell whether to use iana-zones vs timezone vs utc-time.

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