ghl_get_custom_values

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly indicates a read-only listing operation ('List all') and clarifies the scope ('in the location'), which is meaningful. It does not go into pagination or permissions, but for a simple list tool this is adequate and adds value beyond the bare name.

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 is front-loaded with the verb and resource. Every word is meaningful, and there is no wasted text or repetition of the tool name.

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 parameterless list operation with no output schema, the description is sufficiently complete: it states the resource, the scope, and the action. It does not mention response format or limitations, but these are not critical given the simplicity. The clarification of 'location-level variables' adds useful context that helps distinguish from custom fields.

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 tool has zero parameters, so the baseline is 4. The description adds context about what is being listed (custom values as location-level variables), which compensates for the absence of schema detail. No parameter explanations are needed.

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 (List), the resource (custom values), and provides a clarifying parenthetical ('location-level variables') that distinguishes it from related concepts like custom fields. It is specific and differentiates from sibling tools like ghl_get_custom_fields and ghl_create_custom_value.

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 clearly implies when to use this tool (when you need to retrieve all custom values for the location), and the context 'in the location' sets expectations. However, it does not explicitly mention exclusions or alternative tools, though the sibling set makes the purpose unambiguous.

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