ghl_custom_field_update_folder

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

Annotations provide readOnlyHint=false, destructiveHint=false, idempotentHint=true, indicating a safe update operation. The description adds the endpoint URL and OAuth scopes, which are helpful. However, the misleading create statement detracts from 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?

Description is short but contains messy HTML and a redundant/contradictory div ('Create Custom Field Folder'). The structure is not clean; the info block and endpoint details are useful but poorly formatted.

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?

No output schema, so the description should ideally explain what the response contains or how the folder is updated. It only provides the endpoint and scopes. Missing details on return value, error handling, or side effects beyond annotations.

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?

Input schema already provides descriptions for 'name' and 'locationId' (e.g., 'Field name', 'Location Id'). The description does not add further semantic meaning beyond what the schema provides. Schema coverage is moderate, so baseline score of 3 is appropriate.

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 states 'Update Custom Field Folder Name' which clearly indicates updating a folder name. However, a div inside the description says 'Create Custom Field Folder', causing confusion. The purpose is mostly clear but undermined by the contradictory create statement.

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?

No explicit guidance on when to use this tool versus alternatives like ghl_custom_field_create_folder. The info note mentions scope limitation to Custom Objects and Company, which implicitly suggests usage context, but no clear when-to-use or alternatives.

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