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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds a valuable behavioral nuance: the DEFAULT timezone fallback rule, which is not inferable from annotations. It does not repeat annotation info.

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 concise and front-loaded with the core action. It uses only a few sentences to convey purpose, usage, and a default fallback. No filler or redundancy (the repetition in the input is a formatting artifact; the actual description is tightly written).

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 zero parameters, rich annotations, and no output schema, the description provides complete context: it lists the kind of data returned (IANA identifiers, abbreviations, UTC offsets), specifies 'all available' (no filtering), and includes the default fallback value. This is sufficient for an agent to select and invoke the tool correctly.

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 has zero parameters, and the schema coverage is 100% (by triviality). The description needs no parameter explanations. With 0 params, the baseline is 4, and the description does not attempt to add unnecessary parameter context.

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 tool's function: 'Get all available timezones with IANA identifiers, abbreviations, and UTC offsets.' This is a specific verb+resource combination that distinguishes it from sibling reference tools like fetch_countries or fetch_states.

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 states when to use: 'Use this tool whenever a timezone needs to be determined for any operation.' It also provides a fallback rule (TimezoneId 7) when the correct timezone cannot be determined, giving clear contextual guidance.

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