Create GoHighLevel Custom Value

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

The description labels the tool as a 'Write operation' and adds a caution against live data use, which supplements the annotations (readOnlyHint=false, openWorldHint=true). However, it does not detail side effects, idempotency, or potential errors, missing opportunities for deeper transparency.

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 with two sentences, no redundant information. The structure is front-loaded with purpose followed by a usage constraint. However, it could be slightly more informative without sacrificing brevity, earning a 4 rather than a 5.

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?

Despite 4 parameters and no output schema, the description fails to explain what a custom value is, how it relates to the GoHighLevel ecosystem, or what the return value of the operation looks like. The mandatory parameters and response format are left entirely to the schema, making the description incomplete for a tool with moderate 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?

With 100% schema coverage, the baseline is 3. The description adds no parameter details beyond what the schema provides (e.g., it does not explain the meaning of 'name' or 'value' in the context of custom values), so it neither adds nor detracts from schema coverage.

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 'Create a custom value for a GoHighLevel location,' using a specific verb and resource. It distinguishes itself from sibling tools like ghl_create_custom_field by explicitly naming 'custom value', making its purpose unambiguous.

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 a warning about not running against live data without approval, but lacks guidance on when to use this tool versus alternatives like ghl_update_custom_value or ghl_delete_custom_value. No context on prerequisites or typical scenarios is given.

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