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

No annotations are present, and the description does not disclose side effects, read-only behavior, or the fact that most schema parameters are discarded. The schema's per-parameter notes are not summarized at tool level.

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 focused sentence with no redundant detail. It is front-loaded with the key term 'IANA timezone names'.

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?

The description does not state whether a call needs no arguments, what the output format is, or how to verify a zone name. With a misleading broad schema and no output schema, this is insufficient for correct use.

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 tool-level description does not explain how any of the nine optional parameters relate to retrieving common timezone names. Most parameter descriptions are irrelevant to timezones (e.g., 'Git ref name', 'JSON text to validate'), leaving agents confused.

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 tool's resource—common IANA timezone names for clock calls—and aligns with the tool name. It does not use an action verb but is still clear enough to convey what is provided.

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?

It gives only the vague context 'for clock calls' and does not state when to choose this tool over siblings like timezone or utc-time. There is no guidance on invocation or filtering.

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