ghl_create_contact

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

With no annotations, the description carries the full behavioral disclosure burden. It discloses that the operation requires a specific write scope and that it seals a ProofLink receipt, adding some transparency. However, it does not mention side effects, failure modes, or idempotency, leaving gaps for an agent.

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, consisting of two sentences that front-load the core purpose and follow with the scope and receipt information. Every sentence adds distinct value without redundancy.

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 absent schema descriptions and lack of output schema, the description is under-specified for a six-parameter tool. It fails to clarify required fields, parameter formats, or return behavior, leaving significant information gaps for an agent to select and invoke the tool correctly.

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 schema provides no descriptions for the six parameters, and the description does not compensate by explaining their meaning or format. The description only names the tool's purpose, offering no additional semantic guidance for parameters such as first, last, email, phone, company, or tags.

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 action (create a contact) and the target system (GoHighLevel CRM), distinguishing it from sibling tools like ghl_update_contact and ghl_send_email. The additional mention of ProofLink receipt sealing adds a secondary behavior but does not obscure the primary purpose.

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 does not provide explicit guidance on when to use this tool versus alternatives. It mentions a required scope but lacks any exclusions or alternative tool references. The usage is only implied by the verb 'create', not elaborated.

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