Create Calendar Event

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

Annotations already indicate this is a write operation (readOnlyHint=false), non-destructive, and openWorld. The description adds no additional behavioral context beyond stating the action, so it meets the baseline without enriching beyond annotations.

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 concise sentence that immediately conveys the core purpose. There is no unnecessary detail or repetition, making it highly efficient.

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 simple create operation, the description adequately covers the action. While there is no output schema or detailed side-effect information, the tool's straightforward purpose and informative schema make the description sufficient. It could mention more about prerequisites or return values, but it is not critically incomplete.

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 73%, which is moderate. The description itself mentions no parameters, but the schema provides descriptions for most fields. Since 27% of parameters lack descriptions (e.g., locationId, appointmentStatus), the description could have compensated but didn't, keeping this at baseline.

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 identifies the action ('Create') and the resource ('a new appointment/event on a GHL calendar'), making it easy to understand what the tool does and distinguishing it from siblings like ghl_update_event or ghl_delete_event.

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 provides no guidance on when to use this tool versus alternatives. While the sibling names suggest related event operations, the description does not explicitly state exclusions or mention when to choose this over update/delete/list tools.

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