ghl_location_get_timezones

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the endpoint and OAuth scopes, which are beyond annotations. No additional behavioral traits (e.g., rate limits, pagination) are disclosed.

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 includes redundant lines ('Fetch Timezones' and 'Fetch the available timezones') and implementation details (endpoint, source file) that are not essential for an AI agent. Could be more concise.

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?

For a simple read-only tool with one parameter, the description covers purpose, parameter, and OAuth scope. It does not mention the response format (e.g., returns an array of timezone strings), which would add value. Adequate but not complete.

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?

Schema coverage is 100% (only parameter locationId with a description). The description does not add any additional meaning about the parameter beyond the schema. Baseline 3 for high coverage.

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 states 'Fetch Timezones' and 'Fetch the available timezones', clearly indicating the tool retrieves timezones for a location. The verb and resource are specific. It does not explicitly distinguish from sibling tools, but the name and context make it obvious.

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 provides OAuth scopes (locations.readonly) and the endpoint, implying it is a read operation. However, it does not explicitly state when to use it vs alternatives or provide any exclusions, leaving usage guidance implicit.

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