Create GoHighLevel Appointment

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

Explicitly states it is a write operation (consistent with annotations), and adds a warning about live data usage. However, does not disclose other behaviors like side effects, required permissions, or response contents.

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?

Concise at two sentences, front-loading the core action and endpoint. However, the structure is minimal and could be expanded to include parameter hints without becoming overly long.

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?

Incomplete for a tool with 13 parameters, no output schema, and complex nested objects. Lacks explanation of required vs optional parameters, return value, or usage examples.

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 description coverage is low (46%) and the tool description provides no additional meaning about any parameters. The description fails to compensate for the schema's lack of parameter details.

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?

States the action 'Create an appointment' and specifies the endpoint 'POST /calendars/events/appointments', making the purpose clear. However, it does not differentiate this tool from sibling tools like ghl_update_appointment or ghl_delete_appointment.

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?

Only provides a caution about not running against live data without approval. No guidance on when to use this tool versus alternatives (e.g., ghl_update_appointment for modifications) or prerequisites.

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