get_available_slots

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the basic purpose without mentioning that the tool returns available slots, whether it is read-only, or any authentication requirements. The agent is left guessing about side effects and output format.

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 9-word sentence, which is under-specified. It lacks structure and does not efficiently convey necessary information. True conciseness would include key points like the date-range filtering and timezone handling without fluff.

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 absence of an output schema and annotations, the description is incomplete. It does not explain what the return value is (e.g., list of time objects), error conditions, or how the timezone parameter affects results. The tool's complexity (4 params, date constraints) warrants a more thorough description.

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 100% coverage with each parameter described (calendarId, startDate, endDate, timezone), so the schema does the heavy lifting. The description adds no additional semantic value beyond what is already in the schema, earning a baseline score of 3.

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 'Get' and the resource 'available GoHighLevel booking slots for a calendar', which is specific and distinct from sibling tools like list_calendars or list_events. However, it could be more precise by mentioning 'checks for availability within a date range'.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include calendar and event listing operations, but the description does not clarify that this tool is specifically for checking booking slot availability, nor does it mention prerequisites or exclusions.

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