locations_get_timezones

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is well covered. However, the description adds no behavioral context beyond the annotations—it does not mention default behavior (which is in the schema) or any edge cases. Since the description doesn't add value over annotations, it scores low on this dimension.

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 extremely concise—only three words—which is efficient but under-informative. It is not poorly structured, but it borders on being too terse. A single sentence explaining the purpose and possibly the return type would be more helpful without adding much length.

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 the tool has no output schema and only one optional parameter, the description still fails to convey what the response will contain (e.g., a list of timezone IDs, names, offsets) or any limitations. While annotations cover safety, the description leaves critical details about the return value implicit, making it incomplete for an agent to fully anticipate 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?

The schema covers the single parameter 'locationId' with a description including its default behavior ('Defaults to GHL_LOCATION_ID when omitted'), so schema coverage is 100%. The description itself adds no parameter information. According to the rubric, with high schema coverage, a baseline of 3 is appropriate because the description doesn't need to repeat schema details.

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 'Fetch Timezones' is a terse restatement of the tool name and provides only a verb and resource without any scope or detail. It does not clarify whether this returns timezone identifiers, offsets, or something location-specific. There are no sibling timezone tools to distinguish from, so the lack of differentiation is less critical, but the purpose is still vague.

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 gives no guidance on when to use this tool versus alternatives, no context about prerequisites, and no exclusions. Even for a simple read operation, some indication of typical use cases (e.g., 'to retrieve timezone settings for a location') would be helpful. The absence of any usage direction leaves the agent to infer entirely from the name.

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