list_timezones

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

With no annotations provided, the description carries full burden for behavioral disclosure. It clearly discloses the worst-case behavior (returns all 7,072 entries at once), which is the most critical behavioral trait for an agent to know. The description does not contradict any annotations (none exist), and offers key context about data size.

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 sentence that packs crucial information: what is returned, how many items, and the lack of pagination. Every word serves a purpose, and it is appropriately sized for a zero-parameter tool.

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 there are no parameters, no annotations, and an output schema exists (which presumably describes return structure), the description covers the essential behavioral context. It could optionally mention response size or performance impact, but the core completeness for safe agent usage is met.

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 has 0 parameters, and schema description coverage is 100%. The description adds no parameter-level detail because there are no parameters to document. A score of 3 is baseline since the schema already fully describes parameter expectations.

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 states the verb 'List' and the resource 'all 7,072 available city/timezone entries'. It distinguishes itself from sibling tools, none of which deal with timezone listing, by being the only tool in the sibling set with this purpose.

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 description explicitly flags that there is no pagination and that all entries are returned at once. This warns the agent about potential large data transfer, which is helpful context. However, it does not mention when to use this tool versus local timezone handling or other date-related tools, which limits the score.

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