Create GHL Calendar

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

Annotations already indicate this is a write operation (readOnlyHint: false). The description adds no additional behavioral context beyond that—no mention of side effects, idempotency, return values, or required permissions. It does not contradict annotations, but provides no extra value.

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, clear sentence with no wasted words. It is front-loaded and easy to scan.

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 create operation with no output schema, this description is incomplete. It does not mention what the operation returns (e.g., calendar ID, booking page URL) or any required context like locationId. Given 5 parameters and moderate complexity, more detail is necessary.

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 description does not elaborate on any parameter meaning. Schema description coverage is only 40%, with three params (locationId, description, calendarType) lacking descriptions. Since the description fails to compensate for this gap, parameter semantics remain poorly communicated.

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 ('Create') and resource ('a new calendar in GoHighLevel'), distinguishing it from sibling tools like listing or getting calendars. It is specific and unambiguous.

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 such as ghl_create_event or ghl_update_calendar. The description simply states what it does without mentioning prerequisites, like needing a locationId, or exclusions.

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