ghl_calendar_service_booking_create

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

The description adds minimal behavioral context beyond annotations. It does not explain idempotency, side effects, or the meaning of the openWorldHint. Annotations already indicate non-read-only and non-destructive, but the description repeats little.

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 concise with four lines covering purpose, endpoint, and OAuth scopes. It is well-structured but could be slightly improved by front-loading the most critical usage information.

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's complexity (nested objects, no output schema), the description is insufficient. It lacks information about return values, error conditions, and behavior of optional flags like overrideAvailability.

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 provides comprehensive descriptions for all parameters (100% coverage). The description adds no additional parameter insight, so the baseline score of 3 is appropriate.

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 'Create Service Booking' and 'Create a new service booking', along with the endpoint and OAuth scopes. It identifies the resource and action, distinguishing it from other calendar tools like appointment creation, though not explicitly.

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 (e.g., ghl_calendar_appointment_create). There are no prerequisites, exclusions, or context for when it is appropriate to create a service booking.

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