ghl_create_email_builder_template

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

With no annotations, the description carries full burden. It discloses that it handles both skeleton creation and HTML upload in one call and returns the template ID. However, it omits prerequisites, permissions, validation behavior, or failure modes, leaving notable gaps.

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?

Three concise sentences, each providing distinct value: purpose, operational behavior, and return value. No redundancy or wasted words.

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 3-parameter create tool with no output schema or annotations, the description adequately communicates the dual-step operation and the critical return value (template ID) for use in workflows. Minor gaps like error handling or uniqueness constraints are not addressed, but overall it is sufficient for the complexity.

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 already describes all parameters (100% coverage), so the description adds little beyond referencing HTML content and the returned template ID. It does not elaborate on parameter constraints or formatting beyond the schema.

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 tool creates a new HTML email template in a specific location (GHL Marketing → Emails). It also highlights the combined operation (skeleton + content upload) and the return of a template ID, which distinguishes it from sibling tools like get/update/delete.

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?

Usage is implied by the verb 'create' and the resource, but there is no explicit guidance on when to use this vs alternatives (e.g., updating an existing template). No exclusions or alternative tool mentions are provided.

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