Get free appointment slots

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the tool returns available booking slots for a calendar/range, but it does not disclose output format, pagination, or how timezone affects slot availability.

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 two concise sentences with no filler. The core purpose is front-loaded, and the second sentence pragmatically clarifies the date parameter format. Every word earns its place.

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 required call parameters are mostly covered by the schema, but there is no output schema, and the description does not describe the return shape or what qualifies as a 'free' slot. It also omits timezone behavior. This leaves the tool usable but not fully self-contained.

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 already documents startDate, endDate, and timezone clearly. The description adds only slight meaning for calendarId through 'for a calendar' and repeats that startDate/endDate are epoch milliseconds. With 75% schema coverage, the description is adequate but not highly additive.

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 a specific verb and resource: 'Get available booking slots for a calendar within a date range.' This clearly distinguishes it from sibling tools like ghl_create_appointment and ghl_get_calendar_events, since it focuses on availability rather than creation or existing events.

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 implies when the tool is useful: when you need free slots for a given calendar and date range. However, it offers no explicit guidance about alternatives or when not to use it, even though siblings like ghl_get_calendar_events and ghl_create_appointment exist.

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