Send GoHighLevel Message

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

The description adds value beyond annotations by requiring confirmation and owner approval, which expands on the destructiveHint annotation and provides important safety context.

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 extremely concise with only two sentences, containing no fluff while conveying key requirements.

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 11 parameters, nested objects, and no output schema, the description is insufficient. It does not explain 'outward-facing', how to use the extra field, or return format.

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 coverage is 64%, meaning several parameters lack descriptions (subject, toEmail, fromEmail, attachments). The description does not compensate for these gaps, leaving ambiguity about parameter usage.

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 sends an outward-facing message and provides the endpoint, but does not differentiate it from sibling tools like ghl_search_conversations.

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 mentions a precondition (confirm=true and owner approval) but does not provide guidance on when to use this tool versus alternatives, such as when to use an email vs SMS.

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